API, webhooks, and DDEX orientation
Work out which SpaceMedia API you need, what webhooks are for, and where the technical documentation lives.
This page helps you pick. The technical reference is docs.spacemedia.uk.
Which API
| You want to | Use |
|---|---|
| Create artists, releases, tracks, and deliver catalog | Delivery API |
| Manage members, billing, add-ons, smartlinks, branding | Delivery API |
| Pull royalty reporting, analytics, exports, payout operations | Reports API |
| Exchange DDEX ERN messages with a partner | DDEX Gateway, part of the Delivery API |
The two APIs are separate products on separate hosts with separate credentials. A Delivery API token is rejected by the Reports API, and the Reports API uses a tenant reference that is not your organization reference.
Getting credentials
An organization admin creates them under Settings > DDEX Gateway, which requires the Enterprise API feature. See DDEX Gateway.
Webhooks
Webhooks push DDEX lifecycle events to your endpoint instead of you polling. They are signed, retried on a fixed backoff schedule, and gated on the Enterprise Delivery API add-on.
Verify the signature on every delivery. Treat the payload as a notification to act on, not as authoritative state: read current state back from the API before making a decision on it.
Start here, in order
Support
Integration questions go through authenticated Enterprise tickets with the operation, environment, UTC timestamp, public reference, HTTP status, and sanitized error body.