Jump straight to your product's support page:
Join Information Architect and API Evangelist Lou Powell at Vanick Digital and API Testing Advocate Paul Bruce as they discuss how to successfully launch and grow your API strategy to meet the increasing demands on your team and skills.
Join API Implementation Strategist Andrew Fullen of Sogeti and API Testing Advocate Paul Bruce as they discuss how to overcome challenges in integration between API tools, back-end systems, and the teams that deliver them.
Strictly speaking, SOAP and REST aren't directly comparable: REST is an architectural style, and SOAP is a specific protocol defined by a standard. A REST-styled project might, in principle, rely on SOAP. However, architects often abbreviate a typical choice in these terms: SOAP involves
In order to fully understand how your target audience would use your API, you have to dogfood it yourself and then, once it’s out in the wild, you need to monitor how it’s being used. For both API testing requirements, let’s use the common REST API example of a simple contact
Representational state transfer or “REST” is the software architectural style designed for distributed systems and, particularly, the World Wide Web. REST is not a protocol or standard. REST architecture is simply following certain guidelines for how a well-designed Web app behaves, in a
The machine-to-machine communications APIs enable are so important that the literature and contention around REST have multiplied in the following years. Several principles of successful REST APIs have emerged, though; a dozen of the most important follow.
While API performance is crucial for success, what we often see during the API delivery lifecycle is that in an absence of additional resources during development, performance problems are often pushed aside until the very end of a project. The goal of these eBook is to provide practical advice
Join Performance Monitoring Expert Priyanka Tiwari and API Quality Nut Paul Bruce as they deep-dive into what the data says about the impacts of poor performance for both API providers and those who use these APIs.
Do you have an API strategy? If not, you still deal with lots of APIs. How do you make sure that your implementation in code aligns with your intended design? How do you speed up your build process to get those awesome API designs out the door without com