If it’s true that the eye is the window to the soul, then the Application Programming Interface (API) is the window to the solution.
After all, an API is a way for products to communicate with each other through a well-documented (or not so well-documented) interface just as the eye perceives and communicates with the outside world. APIs allow companies to open up data to external third party developers, consume data from third-party product interfaces, and automate and orchestrate processes prone to human error.
An app developer can leverage a good API with ease and invoke it via a web browser, scripting language, or command line quickly.
These good APIs are a flexible way of extending a product’s capabilities to partners and customers alike. An API is where a product interacts with other products and processes – if it is attractive to the intended consumer it “sells”. It doesn’t matter whether that consumer ultimately pays a price for the API (In my opinion, they shouldn’t.) or for that matter whether internal or external to your organization. The point is that you want the API to be used because it is useful and creates value whether that be in reliable processing, lowered costs, faster time to value, or increased security.
When done right, APIs enable enterprises to innovate faster and reach new audiences, which is why I am writing about them today.
Tripwire has been investing in our APIs for longer than my decade with this company. I run technology alliances, so having an easy way to extend our products capabilities with third-party technologies is central to my role and more importantly to Tripwire’s ability to participate meaningfully in an ecosystem that protects our customer’s data.
This is a Security Bloggers Network syndicated blog post authored by Jim Wachhaus. Read the original post at: The State of Security