Delivery API
The Delivery API connects your own systems to SpaceMedia: create artists and releases, upload audio, run readiness checks, submit for review, track delivery, and drive billing and add-on workflows without anyone opening the dashboard.
Everything is scoped to the organization that owns the credentials. There is no cross-organization access and no organization selector.
Two things before you start
- The Enterprise Delivery API add-on must be active for your organization.
- An admin creates API credentials at Settings > DDEX Gateway. The secret is shown once.
Both are covered in the Enterprise Delivery API guide.
Quickstart
Exchange credentials for a token and make your first request.
Release Lifecycle
The full catalog flow from artist to submitted release.
Endpoint reference
Every operation, generated from the OpenAPI contract.
OpenAPI contract
Download the canonical spec for SDK generation and validation.
Pick your path
| You are building | Read in this order |
|---|---|
| A catalog or delivery integration | Quickstart, Release Lifecycle, Uploads, Metadata Style Guide, Delivery Statuses |
| A billing or checkout integration | Authentication, Checkouts, Rate Limits and Retries |
| A DDEX partner integration | DDEX Gateway, Webhooks, Staging Environment |
| An SDK or client library | Response Conventions, Pagination and Filtering, SDK Generation |
| Anything, before going live | Go-Live Checklist, Troubleshooting |
The five rules that prevent most incidents
- Rehearse on staging first. Staging mirrors production behavior, gives you free add-ons, and never delivers to a store.
- Never retry a write blindly. After a timeout, read the current state before repeating a create, submit, checkout, or install. See Rate Limits and Retries.
- Store public references, not your own identifiers.
release_id,track_id, andcheckout_idare the contract. See Response Conventions. - Tolerate unknown status values. Statuses can be added. Display what you receive rather than crashing. See Delivery Statuses.
- Grant the smallest capability set. New credentials start at
catalog:read. Add nothing you cannot justify. See Authentication.
Every endpoint page is generated from the same OpenAPI specification used for validation and SDK generation. If a narrative page and the contract disagree, stop and report the mismatch rather than guessing.
Environments
| Environment | Base URL |
|---|---|
| Production | https://enterprise.spacemedia.uk |
| Staging | https://staging.spacemedia.uk |
Use separate credentials per environment. Never send production secrets to staging tooling, screenshots, or support tickets.
Contract release notes are published in the Delivery API changelog.
Was this page helpful?