Skip to main content
The UMW Recordings Inc. Developer Platform gives approved partners, labels, and clients programmatic access to UMW’s music distribution network. Through a single REST API, you can manage your full catalog lifecycle — from ingesting metadata and audio assets to delivering releases to global digital stores, tracking royalties across territories, and receiving financial disbursements. Whether you are a label connecting your own systems or a technology partner building distribution tooling, this platform is your complete programmatic interface to UMW’s services.
Access to the UMW Developer Platform requires an approved partner account. To apply, contact your UMW account representative or visit the partner portal to submit a request.

​
Key Capabilities

Catalog Management

Create, update, and retrieve releases, tracks, and associated digital assets. Maintain a complete record of your catalog with structured metadata, ISRC codes, and ownership splits.

Digital Store Delivery

Submit releases for distribution to streaming services and download stores worldwide. Track delivery status, manage takedowns, and configure territory-level availability.

Royalty Reporting

Access normalized royalty records aggregated across territories, stores, and revenue sources. Filter by time period, release, track, or territory for granular earnings visibility.

Payouts and Statements

Retrieve financial statements and disbursement records. Reconcile payout amounts against royalty sources and download structured reports for accounting workflows.

Webhooks

Subscribe to real-time event notifications for key platform activities — including delivery confirmations, royalty report availability, and payout processing milestones.

DDEX Compatibility

Submit and receive catalog metadata in DDEX-compliant formats. The platform supports ERN and RIN message standards for interoperability with industry-standard systems.

​
How the API Is Organized

The UMW Developer Platform exposes a RESTful API that communicates exclusively over HTTPS. All requests and responses use JSON. The API is versioned, and the current stable version is v1. Resources are grouped by domain — for example, /v1/releases for catalog operations, /v1/royalties for earnings data, and /v1/payouts for financial disbursements. Each resource follows standard HTTP conventions: GET for retrieval, POST for creation, PATCH for partial updates, and DELETE for removal where supported. Authentication is handled via Bearer tokens issued to approved partner accounts. All requests must include a valid API key in the Authorization header. See the Authentication guide for full details. New to the platform? Start with the Quickstart guide to request access and make your first API call.