Skip to main content
Integrating with the UMW Developer Platform follows a structured onboarding lifecycle designed to ensure every partner and label can build and validate their integration safely before going live. You begin in an isolated sandbox environment with full API access, then transition to production only after completing certification with the UMW team. The steps below walk you through the complete process — from your initial access request to your first production release delivery.
1

Request Access

To begin, submit an API access request through the UMW partner portal or contact your UMW account representative directly. Your request should include your company name, intended use case, and estimated API usage volume. The UMW partnerships team reviews all applications and will respond within five business days.
API credentials are issued to approved companies only. Individual or personal accounts are not eligible for platform access. Ensure your application is submitted under your organization’s registered legal name.
2

Receive Sandbox Credentials

Once your application is approved, UMW will issue a sandbox API key and a dedicated sandbox base URL. The sandbox environment mirrors production functionality without affecting live catalog data or initiating real store deliveries.Store your credentials as environment variables rather than hardcoding them in your application source code. This keeps secrets out of version control and makes it straightforward to swap credentials when you go live.
Use a secrets manager or environment configuration tool (such as AWS Secrets Manager, HashiCorp Vault, or a .env file excluded from version control) to manage credentials across environments.
3

Make Your First API Call

With your sandbox credentials in place, verify your setup by calling the /v1/stores endpoint. This returns the list of digital stores currently supported for distribution — a lightweight, read-only call that confirms your API key and connectivity are working correctly.
A successful response returns an array of store objects:
If you receive a 401 Unauthorized response, verify that your UMW_API_KEY environment variable is set correctly and that the key has not expired. See the Authentication guide for troubleshooting details.
4

Go Live

After you complete integration development and pass UMW’s certification review, the UMW partnerships team will issue your production API key and confirm your production base URL. The only change required in your application is swapping the sandbox credentials for your production credentials — no code changes are needed.
Production API keys carry full permissions and interact with live catalog data, active store deliveries, and real financial records. Treat production credentials with the same rigor as any sensitive secret. Never commit them to source control or expose them in client-side code.
To schedule your go-live, contact UMW support at developer-support@umwrecordingsinc.com or through the partner portal. The team will coordinate a go-live window and confirm that your account permissions are fully provisioned.

​
Next Steps

With your integration up and running, explore the resources below to build out your full workflow.

Authentication

Understand how Bearer token authentication works, how to rotate keys, and how to handle token errors gracefully.

Sandbox Environment

Learn what the sandbox simulates, how to trigger test events, and how to reset sandbox state between test runs.

API Reference

Browse the full API reference for releases, tracks, stores, royalties, payouts, and more.

Webhooks Guide

Subscribe to platform events and receive real-time notifications for deliveries, royalty reports, and payouts.