Access & environments

What you need before you can make a call, and where to make it.

Getting a Developer-Token

Partner access is provisioned by Zopping (not self-serve today). To get set up:

1. Request a developer credential from your Zopping contact for the retailer's organization. You'll receive a Developer-Token (a long-lived UUID) and the organizationId you'll operate under.
2. Request the RBAC grants your integration needs — access is per resource + method (see Authentication). Tell Zopping which endpoints you need (e.g. "read/write catalogue-service/product, read order-service/order"). Grants are administered centrally.
3. Confirm enabled extensions for the org — some capabilities (multi-store, pricing tiers, returns, custom metadata) only exist if the matching extension is on.

Treat the token like a password. It carries your access and is scoped to one organization.

Environments

• Production — https://zopping.com/api/... (backend gateway) and the retailer's store domain for the storefront gateway.

There is no public self-serve sandbox. To build and test safely, ask Zopping for a non-production test organization / store and exercise the API there. Good hygiene while testing against any environment:

• Operate on a dedicated test store (storeId) so you don't touch live stock or orders.
• Use your own clientIds so test records are easy to find and re-run idempotently.
• Prefer status: "HIDDEN" products and non-live price while validating.

Checklist before your first call

• Developer-Token in hand, sent as Authorization: Bearer <token>
• organizationId known
• RBAC grants for the endpoints you'll call
• Enabled extensions confirmed
• A test store to operate on

Then run the Quickstart.