APIContext + Your Passive Monitoring Stack
Your passive monitoring stack is vital in understanding how your applications, and the APIs on which the applications depend, are being used over time and
APIContext partners with Akamai to expand advanced API monitoring adoption. Learn more >
Your passive monitoring stack is vital in understanding how your applications, and the APIs on which the applications depend, are being used over time and
One of the issues we frequently see is clients having issues with moving to active external monitoring from internal testing or testing through their API
While REST and JSON are in vogue for APIs, there are still plenty of APIs out there using the (not-so) venerable XML-RPC specification, which dates
We know from history that API owners can be poor at communicating changes in their APIs. Twitter, for example, is known for burying the lede concerning API changes at the bottom of otherwise unrelated updates. One client also completely changed their OAuth configuration without actually telling a single user of their APIs. It completely shut off a number of applications. With early warning you can know that something is coming to get you. Or at the very least, you’ll know to contact your service provider for more data – before the dependent apps and services get shut off for good. One of the values of monitoring the APIs…
Marcelo Graciolli licensed under CC BY 2.0 There are many ways to monitor API security on the web. Some APIs might have no security –
One of the things about APIs is that they’re complicated. There’s a lot of things that can and do wrong. So there are many metrics
We support Cookie Authentication using the Post-Conditions section of a test, in conjunction with a multiple-test test run. The general idea would be a test
Copyright APIContext © 2024. All rights reserved.