Catalog

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 and returns a catalogIngestId plus a statusUrl. Ingestion happens asynchronously, so poll statusUrl (honoring the Retry-After header) until the run reaches a terminal succeeded or failed — don't assume success from the 202 alone.

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 items dictionary) cause ingestion to end as failed
• Poll statusUrl to confirm succeeded; a reachable callbackUrl that returns valid JSON is required or the run fails

Poll the status of an async catalog ingest started by Notify Catalog Update, using the catalogIngestId returned in that 202.

Lifecycle (status):

• queued — accepted, not yet started
• pulling — downloading the CatalogSet from your callbackUrl
• processing — validating and building the store catalog
• succeeded — the store now serves the new catalog
• failed — ingestion did not complete; see errors for sanitized, partner-safe reasons

Poll until succeeded or failed, honoring the Retry-After header from the notify response. Returns 404 if no ingest with that id exists for the store.