Skip to main content
Follow this page for customer-facing API changes. Additive changes ship within /v1; incompatible changes require a new major version as described in Versioning.
​
v1breaking

​
Resource identifier migration

Organization, location, and special-closing endpoints now use the current resource identifiers returned by the API. Legacy resource aliases are no longer accepted.Relationship fields—including organization_id, location_id, location_ids, and active_location_ids—use the same identifiers. Pagination cursors also use resource IDs returned by list endpoints.
If your integration stored legacy aliases, replace them with identifiers returned by the current API before making new requests. Treat all identifiers as opaque strings.
​
v1

​
Initial release

The first release of the Chataigne API is available at:
Requests authenticate with a Chataigne API key in the x-api-key header.

​
Included resources

  • Business organization discovery and profile updates.
  • Location discovery, creation, and profile updates.
  • Order, opening-hours, delivery, acceptance, and AI clerk settings.
  • Special-closing management.
  • Location and organization analytics.

​
Shared API behavior

  • Structured error responses and request IDs.
  • Cursor-based pagination and timestamp filters.
  • Idempotency keys for resource creation.
  • Response expansion for organization locations.
  • Per-key rate limits and standard limit headers.