Catalog synchronization using a pull model. You host the CatalogSet JSON on a publicly accessible URL (e.g., S3, CloudFront), then notify Gett when it changes. Gett asynchronously downloads and processes the update.
The CatalogSet format is identical to the Marketfront API — a normalized dictionary structure with catalogs, sections, items, and modifier groups.
Best practices:
- Treat every push as a full replacement (no partial patches)
- Keep item IDs stable across updates to preserve analytics and favorites
- Validate your JSON against the schema before notifying — invalid references cause ingestion failures
Notify Catalog Update
Notify Gett that a store's CatalogSet has changed. Gett will asynchronously download the new CatalogSet from the provided callbackUrl.
This follows a pull model: you host the CatalogSet JSON on a publicly accessible URL, then call this endpoint to trigger a pull. The response is 202 Accepted — processing happens asynchronously.
Best practices:
- Treat every notification as a full catalog replacement (no partial patches)
- Keep item IDs stable across updates to preserve analytics and user favorites
- Validate your JSON against the CatalogSet schema before notifying — invalid references (e.g., an item ID not in the
itemsdictionary) will cause ingestion to fail
query Parameters
storeIdYour internal Store ID
Headers
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Notify Catalog Update › Request Body
callbackUrlURL where Gett can download the CatalogSet JSON
Notify Catalog Update › Responses
Notification accepted. Catalog will be pulled asynchronously.