Skip to main content
A location may have several attached catalogs, but the AI orders from one active catalog. Select it after the catalog exists and, for a complete snapshot, after its synchronization has succeeded.
This operation changes the location-wide selection only. It does not copy, modify, or delete either catalog.

Select a catalog

Send the catalog’s location-scoped public id, as returned by the Catalogs API. Do not send an internal Chataigne database ID.
The request requires catalog.write. The API key must authorize the target location. A successful request returns 200 OK and echoes the selected public ID:
Replacing the selection with the same catalog_id is allowed. To roll back, send the public ID of the previous catalog.

Location scoping

Catalog IDs are unique only within a location. Chataigne resolves catalog_id against the location in the URL and stores the matching private relationship internally. A catalog that does not exist or is not attached to that location returns 404 catalog_not_found. This fail-closed behavior prevents a location-scoped key from selecting another location’s catalog.

Validation and errors

The generated Catalogs API reference in the sidebar contains the complete request and response schemas.