Start here — Getting Started
Eight requests in three folders. The first folder reaches a real200 in two
requests with no account and no API key: it mints a short-lived sandbox key,
stores it in a collection variable, and synthesizes a snippet of speech. Folder 2
walks the submit-a-job / poll-the-status pattern the rest of the API uses, and
folder 3 covers wallet balance and webhook registration.
The full reference
Every public endpoint — 361 requests across 19 folders, covering audiobook, podcast, stems, transcription, text-to-speech, voice management, music and account. Use it as a browsable reference once you know the shape of a call.The reference collection is regenerated from the live OpenAPI document on a
schedule and pushed to the same collection id, so a fork tracks the real API
instead of drifting away from it. The Getting Started collection is
hand-maintained and deliberately small.
Authenticating your fork
Every authenticated request sendsX-API-Key: {{apiKey}}. You have two ways to
fill that in.
- Collection variable
- Environment
- Create an API key in your dashboard.
- Open the forked collection → Variables tab.
- Paste the key into the current value of
apiKey, and leavebaseUrlathttps://api.audiopod.ai.
apiKey still blank, the collection’s pre-request
script stops it with an explanatory message rather than sending an unauthorized
call.
Browse without forking
Getting Started
Eight requests, keyless first call
AudioPod AI API
The full 361-request reference
Next steps
Quick Start
The same flow in cURL, Python and Node.js
API Keys
Create, scope and rotate keys
Webhooks
Get told when a job finishes
