Authenticate using an API key: include the header 'Authorization: Bearer YOUR_API_KEY' on all requests — the API also supports HTTP Basic Auth and OAuth 2.0, but API key authentication is the recommended approach for automated workflows
Create a production by POSTing to 'https://auphonic.com/api/productions.json' with a JSON body specifying at minimum 'preset' (UUID of a saved preset) or inline 'algorithms' and 'output_files' arrays; presets bundle your standard settings for reuse
Upload your audio file to the production via POST to 'https://auphonic.com/api/production/{uuid}/upload.json' using multipart/form-data with the file attached as 'input_file'
Start processing by POSTing to 'https://auphonic.com/api/production/{uuid}/start.json' — Auphonic queues the job and processes it asynchronously
Poll production status via GET 'https://auphonic.com/api/production/{uuid}.json' and check the 'status_string' field — values progress through 'queued', 'processing', and end at 'done' or 'error'; alternatively configure a webhook URL in the production to receive a POST callback on completion
Retrieve output file URLs from the completed production's 'output_files' array and download or forward them to your hosting or delivery system
Known gotchas
Auphonic productions are asynchronous — do not expect immediate results after calling the start endpoint; use webhooks for production workflows rather than polling to avoid unnecessary API calls
The Simple API endpoint ('https://auphonic.com/api/simple/productions.json') creates and starts a production in one call but offers less control over output file formats and outgoing services than the full JSON API
Auphonic accounts have monthly production time credits — large batches may exhaust credits before the month resets; check remaining credits via GET 'https://auphonic.com/api/user.json' before scheduling large jobs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp