Content Negotiation: Stop Creating api/v1/get-json-data

Added: 2026-05-27

[00:00:00]If you are hard-coding data formats into your API endpoints like /data.json or /data.xml, please step away from the keyboard. The architects of HTTP figured out how to solve this over 30 years ago. It's called content negotiation. Content negotiation is the mechanism that allows a single URI to serve entirely different representations of a resource based on what the client actually supports. One endpoint, infinite formats. How does it work? It's all in the request headers.

[00:00:31]The client uses the accept header to tell the server what it wants. For example, accept application.json or application.xml.

[00:00:40]The server reads this, formats the internal state, and responds with a content type header matching the winner.

[00:00:46]But clients can be picky. They use quality values or Q factors to rank preferences from zero to one. If a client sends this string, it prefers JSON, but it will settle for a CSV if your back end doesn't speak JSON.

[00:00:59]And it's not just for file formats.

[00:01:01]Accept encoding negotiates compression like Brotli versus Gzip, and accept language negotiates localization. Your server handles all of this automatically before it even hits your business logic.

[00:01:13]Are you actively using HTTP content negotiation or are you still relying on custom URL extensions? Let's fight in the comments. Follow for hardcore back end architecture.