BREAKING NEWS: BREAKING: APIContext Formed To Create Industry Solutions For API Oversight And IntegrityRead Now >

200 OK? Check Again.

Something we’ve talked a LOT about is when an API returns a HTTP 200 ok code, but the API returns an error. This can be a challenge for a gateway’s passive monitoring and backend services to spot because, technically, nothing went wrong.

Take a look at one we had just this morning from the APIs for a major IoT provider.

HTTP/1.1 200 OK
Date: Wed, 21 Mar 2018 09:10:52 GMT
Server: Apache
Vary: Accept-Encoding

“status”: 2XXX,
“body”: {},
“error”: “An unknown error occurred: Maintenance mode, please check”

It’s vital to have active monitoring that not only spots these problems, but lets you know – before your customers do. And in the world of Open Banking, where this is a regulatory compliance issue, you need to spot these before they trigger a regulator complaint – and you can’t prove it didn’t happen.

Contact APIContext today about how our active monitoring solutions can spot issues like this.


Request A Demo

Find A Slot To See A Demo Or Speak To One Of Our Support Specialists

Ready To Start Monitoring?

Want to learn more? Check out our technical knowledge base, or our sector by sector data, or even our starters guide to the API economy. So sign up immediately, without a credit card and be running your first API call in minutes.

Related Posts

Join Us Now!

Join the 100s of companies relying on APIContext.