Self-service store registration for the Gett network. The onboarding flow:
- Register —
POST /onboarding/storeswith store details and catalog URL - Catalog Pull — Gett automatically downloads and validates your CatalogSet
- Check Status — Poll
GET /onboarding/stores/{id}to track progress - Activate — Once
ready_to_activate, call activate to go live
Status pipeline: pending_catalog → catalog_ingesting → ready_to_activate → active (or catalog_failed if validation errors occur).
Register Store
Register a new store for Order Booster. Provide your internal partnerStoreId, store details, and a catalogCallbackUrl where Gett can pull your CatalogSet.
After registration, Gett automatically pulls and validates the catalog. Poll the status endpoint to track progress through the pipeline: pending_catalog → catalog_ingesting → ready_to_activate (or catalog_failed).
The webhookUrl is where Gett will send order validation and placement requests once the store is active.
Headers
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Register Store › Request Body
partnerStoreIdYour internal store ID
namecatalogCallbackUrlURL where Gett can pull the CatalogSet
webhookUrlURL for order webhooks
Register Store › Responses
Store registration started
onboardingIdpartnerStoreIdstatusOnboarding pipeline status.
pending_catalog— Waiting for Gett to pull catalogcatalog_ingesting— Processing and validating the catalogcatalog_failed— Validation errors occurred (seeerrorfield)ready_to_activate— Catalog validated, ready for activationactive— Store is live on the Gett network
storeIdAssigned after activation
errorError message if status is catalog_failed
createdAtGet Onboarding Status
Check the status of a store onboarding. The status field tracks progress through the pipeline:
| Status | Description |
|---|---|
pending_catalog | Waiting for Gett to pull catalog |
catalog_ingesting | Processing and validating catalog |
catalog_failed | Validation errors (see error field) |
ready_to_activate | Catalog validated, ready for activation |
active | Live on the Gett network |
path Parameters
onboardingIdHeaders
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Get Onboarding Status › Responses
Onboarding status
onboardingIdpartnerStoreIdstatusOnboarding pipeline status.
pending_catalog— Waiting for Gett to pull catalogcatalog_ingesting— Processing and validating the catalogcatalog_failed— Validation errors occurred (seeerrorfield)ready_to_activate— Catalog validated, ready for activationactive— Store is live on the Gett network
storeIdAssigned after activation
errorError message if status is catalog_failed
createdAtCancel Onboarding
Cancel an in-progress onboarding.
path Parameters
onboardingIdHeaders
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Cancel Onboarding › Responses
Onboarding cancelled
Activate Store
Activate the store to go live on the Gett network. Only valid when status is ready_to_activate — calling with any other status will return an error.
Returns the final Store object with its assigned global storeId. After activation, the store will begin receiving order webhooks.
path Parameters
onboardingIdHeaders
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Activate Store › Responses
Store activated
storeIdnamephonetimezonelogoUrldescriptionstatusStore availability state.
online— Store is accepting orderspaused— Store is temporarily not accepting orders (seereasonfor why)