Getting Your Credentials
API Token
To create an API token:- Log in to your Redo Dashboard
- Go to Settings → Developer
- Click Add API Client
- Copy the generated API secret
Store ID
Your Store ID is displayed in the General section of Settings → Developer in the Redo Dashboard.API Endpoints
All API endpoints are authenticated using the Bearer authorization scheme with your API secret. Include your API secret in theAuthorization header of every request:
Example Request
Access scopes
API tokens carry access scopes that determine which protected endpoints they may call. For example, listing returns requiresreturns_read, and a request is
rejected with 403 Forbidden if the token does not hold it.
Choose a client’s scopes in Settings → Developer when you create its
token, and update them at any time without re-issuing the token. Endpoints that
require a scope list it in this reference.
Public storefront coverage endpoints do not require an access scope. A token
used only for those endpoints can be created with no scopes selected.
Tokens created before access scopes were introduced were granted all scopes,
so they keep working unchanged. Newly created tokens only carry the scopes you
select.
Webhooks
Webhooks are authenticated using the Bearer authorization scheme with a secret you provide when creating the webhook subscription. Redo will include this secret in theAuthorization header when delivering
webhook events to your endpoint:
Webhook Event Delivery
- Webhook events are delivered in order for each individual subject (e.g., return)
- If the response is not a 2xx status code, the event will be retried multiple times before discarding it