Keys, webhooks, sandbox
Four pieces of setup, and a sensible order: provision the sandbox first, issue sandbox keys, let the integrator work there, and only then create the production key and the production webhook. Doing it the other way round means the first thing an integrator touches is your live catalog.
Two decisions here are hard to walk back. Scopes get widened during troubleshooting and never narrowed afterwards, so start narrow. And the codes you use — attributes, price lists, channels, import profiles — must be identical in the sandbox and in production, or every mapping breaks at go-live.
- Create an API key — Settings › API keys, scoped and named.
- Set up webhooks — Subscribe your system to events.
- SFTP and file exchange — For the ERP that only speaks CSV.
- Set up a sandbox — Provision, seed, hand to the integrator.
Rate limits, quotas and fair use
The limit is per tenant, not per key — which means your BI job can throttle your storefront. What 429 means, how to back off, and when a loop should have been a bulk job.
Create an API key
Settings › API Keys — name it for the integration, scope it to exactly what it needs, hand the secret over safely, and test it before anyone builds against it.