API Versioning

Vibe pins every request to a specific API revision via the X-Vibe-Revision header. This is how Vibe ships backward-incompatible changes without breaking existing integrations.

How to pin

Add the X-Vibe-Revision header attribute on every request to api.vibe.co:

X-Vibe-Revision: 2026-05

Hard-code your pinned value. Don't derive it from "latest" — that defeats the entire pinning model.

What if I send the wrong value?

Header value	Behavior
A published revision	Request is processed against that revision's behavior.
Unknown or future revision	`400 Bad Request`, error type `unknown_revision`.
Missing	`400 Bad Request`. [verify — could default to a fallback]

What's published

See the Changelog for the current list of published revisions and what changed in each. When a new revision ships, the Changelog entry documents the breaking changes and the migration window.