Quickstart
Ten minutes from credentials to your first authenticated response.
You need: the Enterprise Delivery API add-on active, and an API key and secret created by an admin at Settings > DDEX Gateway. See the Enterprise Delivery API guide if you do not have them yet.
Choose your environment
| Environment | Base URL | Use it for |
|---|---|---|
| Staging | https://staging.spacemedia.uk | Everything you are building. Free add-ons, isolated media, simulated delivery that never reaches a store. |
| Production | https://enterprise.spacemedia.uk | Live automation, after sign-off. |
Build against staging. Use separate credentials per environment and never reuse production credentials in test scripts, screenshots, tickets, or shared playground sessions.
Exchange credentials for a token
The credentials below are production-format placeholders. They are intentionally invalid, so replace them with your own.
curl --request POST 'https://enterprise.spacemedia.uk/api/v1/token' \
--header 'X-Api-Key: 00000000-0000-4000-8000-000000000000' \
--header 'X-Api-Secret: 0000000000000000000000000000000000000000'Keep the returned bearer token and its expires_at. Discard the key and secret from memory: they are never sent to any other endpoint.
Make a safe read
GET /api/v1/countries is the ideal first call. It changes nothing and needs only the default catalog:read capability.
curl 'https://enterprise.spacemedia.uk/api/v1/countries' \
--header 'Authorization: Bearer 0000000000000000000000000000000000000000963fbb8e' \
--header 'Accept: application/json'You are looking for HTTP 200, success: true, and reference values in data.
Confirm what your credential can do
GET /api/v1/me returns the authenticated context. Check the capabilities before you write any code that assumes write access, because new credentials start at catalog:read only.
Run a catalog smoke test on staging
Use fictional records until the integration has passed the Go-Live Checklist.
- Create or reuse an artist.
- Create a draft release.
- Upload audio and keep the returned
audio_file_id. - Create a track with that
audio_file_id. - Save rights and distribution selections.
- Run readiness checks.
- Submit, then poll the simulated review and delivery lifecycle.
Full detail is in Release Lifecycle.
If the first call fails
| Response | What it means |
|---|---|
401 on token exchange | The key or secret is wrong, or belongs to the other environment |
401 on a normal request | The token expired. Refresh it before expires_at |
403 | The credential lacks the capability, or a gating add-on is inactive. Do not retry |
404 | The reference does not exist in your organization |
429 | Slow down and respect Retry-After. See Rate Limits and Retries |
More in Errors and Status Codes and Troubleshooting.
Before you touch live records
Do not point a customer integration at production until you have tested authentication, permissions, retries after timeouts, uploads, checkout behavior, readiness checks, and your support escalation path against safe sample data.
Next
Was this page helpful?
How the API Works
The Delivery API mental model: organization scope, capability-based authorization, add-on gating, response envelopes, and the available endpoint families.
Staging Environment
Production-compatible API rehearsals with free add-ons, isolated media, simulated delivery, and automatic cleanup.