The WBBT Records music distribution API connects your own application to artist accounts, audio and artwork uploads, release delivery, analytics and royalty-reporting workflows. It is a REST API for server-to-server integration, with public developer documentation and an OpenAPI specification. Access is invite-only early access: an eligible Label account and an accepted, signed and paid API offer are required. Your approved agreement defines features, permissions and capacity; a White-Label subscription is not required.
Who is it for?
Music software teams
Connect your existing product to account and release workflows while retaining responsibility for your own interface.
Labels with internal tools
Discuss integration where staff already manage catalogue preparation in another system and need a defined distribution handover.
Artist-service platforms
Plan child-account and submission workflows around your artist relationships, with agreed access and operational responsibilities.
Connect your own music platform
An API lets your application participate in a distribution workflow without requiring every action to begin in a separate dashboard. Start by identifying the data and release actions your product needs to exchange with WBBT. Onboarding documentation defines the available operations; do not assume every dashboard feature has an API equivalent.
Child accounts and artist workflows
The integration supports creating child accounts for your users within the approved scope. Plan how your application associates users with the correct accounts and catalogue records. Your team remains responsible for its user experience and the permissions it grants. Discuss account roles and ownership boundaries before implementation.
Track uploads and release submissions
Upload audio and artwork, create artists, build draft releases and validate submission requirements before review. The API provides reference data for stores, genres, languages, countries and contributor roles. After submission, releases enter WBBT’s normal review workflow. A rejected release that has not gone live can be corrected and resubmitted; live-release changes use the edit-request workflow.
Delivery webhooks and status events
Follow release status, destination selections, platform links and activity records. Signed webhooks cover release approval or rejection, edit approval or rejection and takedown approval. Register endpoints, select events, send test notifications, inspect delivery attempts, rotate signing secrets and retry eligible failed deliveries. Your integration should verify signatures and handle duplicate events safely.
Stream analytics and CSV exports
Read reported listening activity by day, track, release, platform or territory, with partner-wide summaries and CSV exports. Reports expose freshness and coverage information so your application can distinguish a missing value from zero. Country reports can cover a different source period from daily listening data. These are reported analytics, not a live counter of every stream.
Royalty statements and song-level reporting
Read monthly earnings, release-level revenue and statement rows with recording identifiers, platforms, territories and sales periods. Reporting endpoints support grouped totals and CSV export. Source statement receipts, credited earnings and available wallet balance are distinct measures. Royalties follow monthly reporting cycles; a daily listening chart does not mean daily revenue settlement.
Payout requests where enabled
When the payouts capability is included, live-key integrations can manage supported payout destinations, read balances and withdrawal history, and submit withdrawal requests. Requests enter WBBT’s manual payment workflow; the API does not make an automatic money transfer. The active agreement, relevant key permissions and available balance govern access. Test keys cannot store real payout details.
Test and live credentials
Test and live API keys have separate subaccounts, catalogue ownership and webhook endpoints. Test submissions check readiness without entering distribution. Key scopes restrict what an integration can do, so a reporting tool does not need permission to submit or remove releases. Keep keys on your server. Write requests use idempotency keys so retrying the same operation does not create duplicate work.
Plan validation and operational handovers
Map a normal submission and the cases where someone needs to intervene: missing metadata, a rejected release, a correction or a takedown. Decide how your application presents those states to staff and artists. Agree who follows up with support and what record identifiers to include. Automation should preserve a clear path for resolving release issues.
A clear relationship with your own platform
Your team owns its interface and artist experience while WBBT provides the agreed distribution infrastructure. API-powered platforms must display the distribution attribution required by the API terms, such as a small “Distribution powered by WBBT” notice. Review that requirement alongside your proposed user journey before implementation.
Access requirements and early-access scope
An eligible Label account and an accepted, signed and paid API offer are required; White-Label is not a prerequisite. Request an early-access invitation and submit your platform and usage details. Access scopes, enabled features and capacity limits are confirmed through the agreement. A public account signup alone does not activate API access, and capacity increases require an updated offer.
Custom pricing through sales
No fixed API subscription or setup price is advertised here. Provide your expected account count, monthly release volume, asset sizes, integration needs and support requirements. Sales determines the final commercial proposal, including access scope and any underlying subscription requirements. Request the written proposal before committing to a development or launch schedule.
How to get started
Request early-access review
Explain the application you operate, the users it serves and the distribution tasks you want to connect.
Confirm the commercial scope
Confirm the eligible Label account, scope and sales offer, then complete acceptance, signing and required payment.
Review documentation and test
Use the supplied specifications and test credentials to check submissions, events and failure handling.
Agree live activation
Confirm the approved integration scope and operational handover before using live credentials for real releases.
Common questions about Music Distribution API
What can I do with the WBBT music distribution API?
The API covers subaccounts and artists, audio and artwork uploads, draft validation and submission, release status, edits and takedown requests, webhooks, listening analytics and royalty reporting. Payout-request operations require an additional enabled capability. Access remains subject to the agreed features and key scopes.
Do I need a Label subscription?
An eligible Label account is required alongside an accepted, signed and paid API offer. A White-Label subscription is not required. Sales confirms the underlying account and API agreement in your proposal.
Is API access available immediately?
No. The Distributor API is invite-only early access. The team reviews your platform and usage, agrees scope and pricing, and confirms onboarding before activation.
Does the API provide delivery webhooks?
Delivery workflows include events such as approval, rejection and takedown. Confirm the current event schema, signing and retry behaviour in the onboarding documentation before implementation.
Where can developers get API documentation?
Read the public WBBT API documentation and OpenAPI specification linked below. Use the current specification for endpoints, authentication, request fields, webhooks and test behaviour, then discuss your proposed integration with the team.
Does test mode send music to stores?
No. Test submissions validate readiness without entering distribution, and test and live keys use separate subaccounts and catalogue ownership. Live edits and takedown operations cannot be started with a test key.
Does the API pay artists automatically?
No. Where payouts are enabled, the API can submit withdrawal requests to WBBT’s manual payment workflow. Reported royalties, available balance and payment processing are separate stages.
How is API pricing determined?
Sales reviews your expected usage, account count, release volume, integration scope and support requirements, then confirms a written proposal. No fixed public API or setup price is listed.
Should I choose the API or White-Label?
Choose an API discussion when your team maintains its own application and wants an integration. Explore White-Label when you need a branded artist workspace. They are separate early-access options, and sales can help define which fits your operation.