<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>APIs on Nalar</title>
    <link>https://nalar.dev/tags/apis/</link>
    <description>Recent content in APIs on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/apis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP Content Negotiation and Correct Vary Headers</title>
      <link>https://nalar.dev/http-content-negotiation-and-correct-vary-headers/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/http-content-negotiation-and-correct-vary-headers/</guid>
      <description>&lt;p&gt;One URL can sometimes represent the same resource in several formats. An API might return JSON or CSV, while a documentation endpoint might return HTML or plain text.&lt;/p&gt;&#xA;&lt;p&gt;HTTP content negotiation lets a client express which representation it can accept. The server chooses a response and tells caches which request headers influenced that choice.&lt;/p&gt;&#xA;&lt;p&gt;The second part is easy to miss: if the response changes based on a request header, shared caches need the correct &lt;code&gt;Vary&lt;/code&gt; metadata.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contract Tests for Reliable Service Boundaries</title>
      <link>https://nalar.dev/contract-tests-for-service-boundaries/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/contract-tests-for-service-boundaries/</guid>
      <description>&lt;p&gt;Distributed systems fail in an awkward place: each service can pass its own tests while the interaction between two services is incompatible.&lt;/p&gt;&#xA;&lt;p&gt;A provider may rename a JSON field, tighten validation, change an enum, or stop returning a value that a consumer quietly depends on. Contract tests make those cross-service assumptions executable.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-a-contract-is&#34;&gt;What a contract is&lt;/h2&gt;&#xA;&lt;p&gt;A contract describes an observable interaction between a consumer and a provider.&lt;/p&gt;&#xA;&lt;p&gt;For an HTTP API, it might specify:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
