One of the common problems we see with APIs is a HTTP 200 code, but a mobile app, in particular still has problem with the results. That usually means there is a content error in the XML or JSON that the API is returning. APImetrics has always parsed your content for errors but we’re now adding clearer guidance on what those errors mean and where to look for them. In every failure report, even if the API has returned a 200, we are providing additional error reporting information:
Additionally, we will leave you with access to the raw content so you can inspect the result yourself.
If you’re pulling data from an existing web database this makes APImetrics an invaluable aid for spotting when problems might arise that won’t show up in any of your other monitoring services.
