<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Api-Design on Joshua Antony | Tech Blog</title><link>https://blogs.joshuaantony.com/tags/api-design/</link><description>Recent content in Api-Design on Joshua Antony | Tech Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blogs.joshuaantony.com/tags/api-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Returning 200 OK for Everything</title><link>https://blogs.joshuaantony.com/posts/stop-returning-200-ok-for-everything/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/stop-returning-200-ok-for-everything/</guid><description>HTTP status codes are a contract consumed by clients, load balancers, monitoring, and caches. When you return 200 OK for partial failures, every one of these systems is blind.</description></item><item><title>Hybris OCC: A REST Facade Over a Stateful Monolith</title><link>https://blogs.joshuaantony.com/posts/hybris-occ-rest-facade-over-stateful-monolith/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/hybris-occ-rest-facade-over-stateful-monolith/</guid><description>SAP Commerce OCC promises a stateless REST API for headless commerce. Underneath, every request hydrates an HTTP session and routes through the same stateful facades built for the JSP storefront. The API is stateless in contract but stateful in implementation.</description></item></channel></rss>