Response Conventions
SpaceMedia API responses use stable public references and local field names. The same naming style appears in examples, endpoint responses, webhooks when available, and support conversations.
Identifier rules
| Object | Public field |
|---|---|
| User | user_id |
| Member | member_id |
| Role | role_id |
| Artist | artist_id |
| Release | release_id |
| Track | track_id |
| Revenue split | split_id |
| Subscription | subscription_id |
| Checkout | checkout_id |
| Smartlink | smartlink_id |
| Payment method | payment_method_id |
| Package | package_id |
| Invitation | invitation_id |
| Label | label_id |
| Temporary uploaded audio | audio_file_id |
Responses do not include duplicate id and uuid fields. Numeric internal references are not part of the public API. When an upload returns a temporary audio reference, the field is called audio_file_id.
Sample data style
- Use realistic labels, distributors, artists, releases, and track metadata.
- Use production-style fictional domains such as
northstar-distribution.co.ukfor examples. - Use production-format placeholder credentials that are clearly invalid, such as
00000000-0000-4000-8000-000000000000,0000000000000000000000000000000000000000, and0000000000000000000000000000000000000000963fbb8e. - Use stable public references for objects.
- Do not copy customer data, real payment secrets, cookies, or live provider references into examples.
Common questions
Why does the API not return an id field?
Objects carry one purpose-named public reference such as release_id. Internal numeric identifiers are not part of the public contract, and there are no duplicate id and uuid fields to disambiguate.
Can I shorten or re-encode a public reference? No. Store and send it exactly as returned.
Which reference does an upload return?
audio_file_id, and it is temporary. The stable track reference is track_id, returned when the track is created.
What should example data look like in my own tests? Realistic but clearly fictional, using placeholder credentials that cannot work. Never copy customer data, live provider references, or real payment secrets into fixtures.
Was this page helpful?