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: 


See what your APIs look like from the outside.
APIContext gives engineering, product, and customer success teams a shared view of API reliability, conformance, and customer impact — without rebuilding dashboards.
Start free