The Retailgrid Public API uses bearer tokens. Each request must include anDocumentation Index
Fetch the complete documentation index at: https://docs.retailgrid.io/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header with your API key.
rg_live_ and are scoped to a single Retailgrid account.
Generate an API key
- Sign in to app.retailgrid.io.
- Open Settings → Integrations.
- Find the API access card and click Generate API Key.
- Copy the key from the modal.
401 Unauthorized and need to be updated.
Verify a key
The fastest way to check that a key works is to callGET /v1/auth/verify:
Failure modes
| Status | Meaning |
|---|---|
401 Unauthorized | Header missing, malformed, or the key is no longer active (rotated, revoked, or deleted). |
403 Forbidden | Key is valid but does not have access to the requested resource. |
Security guidance
- Never commit keys to source control. Use environment variables, a secrets manager, or your CI’s encrypted variables.
- Rotate on suspicion. Generating a new key in the UI immediately invalidates the previous one. There is no separate revoke step.
- Use a dedicated key per integration where possible - because each account holds one active key today, plan key rotations to align with deploys of dependent services.
- Treat keys like passwords. A leaked key gives full read/write access to your Retailgrid catalog and transactions.
