<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>JSON Schema on API Course</title>
    <link>https://apicourse.com/tags/json-schema/</link>
    <description>Recent content in JSON Schema on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/json-schema/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JSON Schema and API Validation: Defining and Enforcing Your Data Contracts</title>
      <link>https://apicourse.com/json-schema-and-api-validation-defining-and-enforcing-your-data-contracts/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/json-schema-and-api-validation-defining-and-enforcing-your-data-contracts/</guid>
      <description>&lt;p&gt;An API&amp;rsquo;s data contract — what it accepts as input, what it returns as output — exists whether you define it formally or not. Leaving it informal means the contract lives only in documentation prose and developer intuition, is inconsistently enforced, and drifts between what the documentation says and what the code actually handles. JSON Schema provides a standard, machine-readable format for expressing data contracts that can drive validation, documentation, and testing from a single source of truth.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
