---
title: "API Versioning"
description: "1 posts about API Versioning, summarised, each linking to the original."
---

# API Versioning
> 1 posts about API Versioning, summarised, each linking to the original.

## Articles

### [Growing A Platform: Introducing API Versioning In Intercom](https://yomu.fyi/post/growing-a-platform-introducing-api-versioning-in-intercom.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Problem & solution

Intercom introduced API versioning for their REST and Messenger Framework APIs, using their open-source Requisite library, enabling safe, frequent updates without breaking existing integrations. Previously, API changes required advance notice and coordinated migrations, which was unreliable and hindered iteration, so they conducted user research to identify friction points. The versioning system uses ‘version changes’ — single transformations that roll back a model change to a previous version, such as renaming user\_id to customer\_id, allowing controllers to always operate on the latest version and chain multiple changes. Developers can test isolated requests using a specific header and upgrade through the Developer Hub, with the ability to roll back immediately if something goes wrong. This design, inspired by Stripe’s approach, allows Intercom to ship changes more frequently and safely across REST API, Messenger Framework, and webhooks.