<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Evgeny Gil</title>
    <description>The latest articles on DEV Community by Evgeny Gil (@evgenygil).</description>
    <link>https://dev.to/evgenygil</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F673503%2Fb526dd35-e5e5-4110-b67d-9823d579ede5.jpeg</url>
      <title>DEV Community: Evgeny Gil</title>
      <link>https://dev.to/evgenygil</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/evgenygil"/>
    <language>en</language>
    <item>
      <title>I built ApiWatch — a free, developer-friendly API uptime monitor (HTTP + keyword checks)</title>
      <dc:creator>Evgeny Gil</dc:creator>
      <pubDate>Fri, 16 Jan 2026 12:55:12 +0000</pubDate>
      <link>https://dev.to/evgenygil/i-built-apiwatch-a-free-developer-friendly-api-uptime-monitor-http-keyword-checks-47j3</link>
      <guid>https://dev.to/evgenygil/i-built-apiwatch-a-free-developer-friendly-api-uptime-monitor-http-keyword-checks-47j3</guid>
      <description>&lt;p&gt;APIs rarely “hard fail” in a clean way.&lt;/p&gt;

&lt;p&gt;What ApiWatch is&lt;br&gt;
ApiWatch helps you monitor mission-critical API endpoints with confidence, with real-time monitoring and instant alerts when something breaks.&lt;/p&gt;

&lt;p&gt;You can try it here: &lt;br&gt;
&lt;a href="https://apiwatch.eu" rel="noopener noreferrer"&gt;https://apiwatch.eu&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What it does today&lt;br&gt;
Current features are intentionally focused on the “simple but not too simple” sweet spot:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Scheduled checks for HTTP endpoints (status codes, timeouts).&lt;/li&gt;
&lt;li&gt;Optional keyword matching (catch cases where you get 200 OK but the response is actually wrong).&lt;/li&gt;
&lt;li&gt;SSL, port, DNS, and WHOIS monitoring (useful for catching expiring certs and domain issues early).&lt;/li&gt;
&lt;li&gt;Notifications when an endpoint goes down or comes back online (with retries)&lt;/li&gt;
&lt;li&gt;CI/CD integration, disable the monitor from pipeline and enable after the successfull release.&lt;/li&gt;
&lt;li&gt;A shareable status page/widgets for communicating incidents.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;ApiWatch is trying to stay developer-first: quick setup, clear signals, and enough detail to debug without drowning you in noise.&lt;br&gt;
​&lt;/p&gt;

&lt;p&gt;What’s next (and where feedback helps)&lt;br&gt;
ApiWatch is still early, and feedback from teams who run real APIs is the most valuable input right now.&lt;br&gt;
​&lt;br&gt;
If you use tools like UptimeRobot / Better Stack / Kuma, it’d help a lot to hear:&lt;/p&gt;

&lt;p&gt;Which alert channels matter most (Email, Slack, webhooks, SMS)?&lt;br&gt;
​What’s your biggest source of false positives today?&lt;br&gt;
​&lt;br&gt;
What would make you switch? (Terraform/API-based setup, better grouping/tagging, etc.)&lt;br&gt;
​&lt;br&gt;
Try it + roast it&lt;br&gt;
Link: &lt;a href="https://apiwatch.eu" rel="noopener noreferrer"&gt;https://apiwatch.eu&lt;/a&gt;&lt;br&gt;
​&lt;br&gt;
If you comment with your use case (public API, internal microservices, cron endpoints, etc.), it’s easier to prioritize the next features.&lt;/p&gt;

</description>
      <category>api</category>
      <category>monitoring</category>
      <category>showdev</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
