LLM Context

Use this page as compact context for AI coding tools that help build Enterprise API integrations. It is intentionally explicit about what the API does and what tools must not assume.

Base facts

Endpoint families

• Auth and current profile.
• Account settings.
• Artists, releases, tracks, rights, distribution, readiness, and submission.
• Revenue splits.
• Users, members, roles, and permissions.
• Packages, plans, subscriptions, checkouts, credits, and payment methods.
• Add-ons and add-on status.
• Copyright summary, wallet reads, top-ups, and release reads.
• Release review queues.
• Smartlinks, destinations, analytics, and preferences.
• Theme and email theme actions.
• DDEX connections, messages, and validation.
• Signed enterprise webhooks, test deliveries, and replay.
• WordPress OAuth installation, authorization, and catalog reads.
• Feedback.
• Countries and territories.

Public reference rules

Use public reference fields returned by the API:

• user_id
• role_id
• artist_id
• release_id
• track_id
• audio_file_id
• checkout_id
• subscription_id
• smartlink_id
• review_id

Do not invent internal selectors or rely on generic id fields unless the endpoint specifically documents one. Do not expose internal numeric references.

Workflow order for release delivery

1. Create or reuse artists.
2. Create the release.
3. Upload audio.
4. Create tracks with audio_file_id.
5. Attach or reorder tracks.
6. Save license, rights, territories, and distribution selections.
7. Run release readiness checks.
8. Submit the release.
9. Poll review and delivery states.

Do not submit before metadata, rights, artwork, tracks, and destinations are complete.

Pagination

Paginated responses include meta. Clients should read:

• current_page
• last_page
• per_page
• total
• from
• to

Stop pagination when current_page reaches last_page, or when the next page returns no data.

Retry and idempotency

• Retry reads with backoff.
• Do not auto retry create, checkout, submit, install, top-up, or publish actions after timeout.
• Read current state before repeating high-impact operations.
• There is no global idempotency key unless an endpoint page says so.
• Treat audio_file_id as temporary upload data.
• Treat embedded_checkout_token as short-lived payment data.

Webhooks

Signed enterprise webhooks exist and are documented. See Webhooks for the subscription lifecycle, signature verification, and retry schedule, and the Enterprise Webhooks endpoint group for the operations themselves. Webhook routes are gated on the Enterprise Delivery API add-on, so confirm the organization has them before assuming delivery. Where an organization has no webhook subscription, fall back to the documented polling endpoints.

Forbidden assumptions

AI tools must not:

• Add organization selectors to public requests.
• Use internal numeric references.
• Invent endpoints that are not in the OpenAPI spec.
• Rename public references into generic fields.
• Log API secrets, bearer tokens, payment tokens, or webhook secrets.
• Assume all destinations share the same delivery behavior.
• Assume sent means live on every DSP.
• Assume checkout creation is safe to retry automatically.
• Assume acting-for-user behavior applies to every endpoint.
• Use backend, database, queue, or storage implementation terms in customer-facing docs.

Good support data

When generating support messages or logs, include:

• Endpoint and HTTP method.
• Public reference.
• Timestamp and timezone.
• Status code.
• Sanitized error body.
• Client version.

Do not include secrets or provider payment references.