The v1 policy

Everything lives under /api/v1. Changes to v1 are additive: new operations, new optional fields, new enum values.
Existing fields do not change type or meaning, and required request fields are never added to an existing operation.
Anything breaking would ship as a new version namespace with a long overlap period, never as a silent change to v1.
Be tolerant in what you read: ignore response fields you do not recognise, and treat unknown error codes like DOMAIN_RULE.

One contract, everything generated

Every operation is defined once, in a typed contract. From that single definition we generate the OpenAPI document, the TypeScript SDK, the Swift SDK, and every page of this reference. A repository gate regenerates and diffs all of them on every change, so an endpoint cannot ship without its documentation and SDKs shipping in the same change.

Current contract

https://www.membber.com/api/v1, 179 operations across 41 domains, spec version 1.0.0.

Changelog

A published, diff-generated changelog is coming: it will be produced from the contract history the same way these pages are produced from the contract, so it can never miss a change. Until it ships, this page always reflects the current surface, and additive changes appear here the moment they reach production. If you need to track a specific operation today, tell us and we will notify you of changes to it.