Public API: Master Audio with One HTTP Request
The most frequent request from teams writing to our support inbox: "can we call your mastering from our code?" Now the answer is officially yes: Magic Master has a public REST API, documented at magicmaster.pro/developers.
Who it's for
- Distribution services — automatic catalog mastering before delivery to the platforms.
- Music generators — post-processing of AI tracks (including the automatic De-clipper for over-compressed exports).
- Labels and studios — batch processing of releases: Album Mode preserves the relative loudness of tracks.
- Indie developers — a mastering feature in your app without hiring a DSP team.
What it looks like
curl -X POST https://magicmaster.pro/api/v2/master \
-H "X-API-Key: mm_live_YOUR_KEY" \
-F "file=@track.wav" \
-F "style=edm" \
-F "target_lufs=-9"
# → {"job_id": "..."} — then poll the status and download the file
Three endpoints cover the whole flow: analyze (free analysis — LUFS, True Peak, genre suggestion), master (1 token = 1 track), batch (up to 10 files, album_mode=1, intensity 0.5–1.5). The response carries the full passport: actual LUFS, post-codec true peak, tonal analysis, a loudness graph.
Honest terms
- Same price as the web app: 1 token = 1 master. No separate "enterprise markup" for API access.
- Analysis is free — build your catalog QC on it and pay only for mastering.
- We don't store files: processing happens in memory, results are deleted after download.
- Interactive docs: magicmaster.pro/docs (OpenAPI/Swagger) — try requests right from the browser.
Getting started
- Sign up and top up your token balance.
- Create a key in your profile.
- Open the developer documentation — quickstarts in curl and Python.
Questions and API requests — support@magicmaster.pro. Tell us what you're building: real integrations drive our API roadmap first.