<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>api monitoring on Abbreviatory.com</title>
    <link>https://abbreviatory.com/tags/api-monitoring/</link>
    <description>Recent content in api monitoring on Abbreviatory.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://abbreviatory.com/tags/api-monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Watch an API for New Errors With curl and Run History</title>
      <link>https://abbreviatory.com/how-to-watch-an-api-for-new-errors-with-curl-and-run-history/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/how-to-watch-an-api-for-new-errors-with-curl-and-run-history/</guid>
      <description>Plenty of APIs answer 200 OK and put the trouble in the body. A catalogue export says &amp;quot;status&amp;quot;: &amp;quot;partial&amp;quot;, and three of its 2,500 items carry an error object saying the price feed is stale. The status code says all is well, and the 720 kB of JSON is too much to read every time someone checks.
The response in this example is the catalogue export from our test fixtures, fetched with curl -si from a local server: 37,534 lines with the headers.</description>
    </item>
    
  </channel>
</rss>
