Changelog
What changed in the brand API and which contract revision is current.
Privacy and analytics
We use necessary technical cookies and, only with your consent, analytics and marketing pixels to improve the website and measure campaigns.
What changed in the brand API and which contract revision is current.
What changes in the brand API that an integration can notice, newest first. The date of the first entry is the contract revision: it comes in X-Nomad-Api-Revision and in info.version of openapi.json. Changing the shape of a published operation requires an entry here; a test checks it on every code change.
New operation conversation.uploads.prepare: the signed upload of one file for a message (25 MB), so the apps and a token can now send attachments with conversation.messages.send and conversation.threads.start.
The contract now keeps a changelog and the revision it announces is that of its newest entry (X-Nomad-Api-Revision header and info.version of openapi.json). New: 500 internal_error for a fault of ours that repeating the call will not fix (it was 503 unavailable), only over the API with a token; Accept-Language chooses the language of the text Nömad writes; reads carry an ETag and answer 304 to If-None-Match; an operation being retired says so with Deprecation, Sunset and Link: rel="successor-version"; brands.list takes limit and cursor and returns nextCursor; orders.list, activity.list and publishing.ideas.list page with a cursor that does not shift when new rows arrive. Same day (roles and credentials): an operation that moves money (changing or cancelling the plan, buying) asked with a token or a service account no longer runs at once: it answers 202 approval_required and waits for its holder to approve it in Nömad; and a token can be narrowed to specific operations, outside which it answers 403 insufficient_scope naming the operation. Between 2026-10-25 and today the contract grew unrecorded: only new operations and new optional fields.
First revision: one method per capability at POST /api/v1/{operation}, personal tokens and service accounts, RFC 9457 problems, Idempotency-Key and RateLimit headers.