API Documentation

Get and store an API key

Authentication belongs on your application server. Never place a production key in browser code, a mobile bundle, logs, or a public repository.

1. 1Create an account and open the API key area in the dashboard.
2. 2Copy the key once, then store it in your server's secret manager or encrypted environment.
3. 3Send it in the Authorization header as a Bearer token and rotate it immediately if exposed.

Quick Start

Create an asynchronous music task, save the returned workId, and poll the feed endpoint for completion. The request below is ready to run after setting your server key.

export UDIOAPI_KEY='replace-with-your-server-key'

curl --request POST \
  --url 'https://udioapi.pro/api/v2/generate' \
  --header "Authorization: Bearer $UDIOAPI_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
    "model": "chirp-v5-5",
    "gpt_description_prompt": "Warm indie pop with acoustic guitar",
    "make_instrumental": true
  }'

# Save workId from the response, then poll:
curl 'https://udioapi.pro/api/v2/feed?workId=YOUR_WORK_ID'

The tracked source files use UDIOAPI_KEY, bounded polling, structured errors, and no third-party dependencies. Remove all secrets before publishing a fork on GitHub.

API Endpoints

Use /v2/generate as the default Music Generate endpoint. MiniMax is an integrated provider available through /v2/minimax/generate, not the default music generation model.

Error handling

Treat the HTTP status and structured response body as part of the integration contract. Log the workId and your own request ID, but never the API key.

Do not retry moderation failures or other terminal task failures. Surface the returned fail_message or error_message so the user can change the input.

Changelog summary

Compatibility-relevant API changes are summarized in this documentation entry and linked to the affected endpoint.