Getting started

Make your first request, then compose the atomic Podcast workflow.

Create an API key

Open Account > API key in your intended Space. Create a key and store it in your application’s secret manager. The credential uses that account and Space for project access and billing.

Send a request

The API origin is https://api-services.podcastor.ai. All Podcast JSON endpoints begin with /open/podcast/v1.

export PODCAST_API_ORIGIN="${PODCAST_API_ORIGIN:-https://api-services.podcastor.ai}"
# Set PODCAST_API_KEY securely in your environment.
curl --fail-with-body "$PODCAST_API_ORIGIN/open/podcast/v1/projects?page=1&page_size=20" \
  -H "X-Api-Key: $PODCAST_API_KEY"

Send ordinary JSON for request bodies, with Content-Type: application/json. Use X-Api-Key; the JSON API does not accept an OAuth Bearer token.

To use another enabled deployment, set PODCAST_API_ORIGIN to its origin before running the example. Include the scheme and optional port, but no /open/podcast/v1 suffix. The examples append that path themselves. Use credentials issued by the target environment. A local documentation preview still calls the production API unless you explicitly replace the API address.

Responses use the shared envelope:

{"code": 0, "msg": "success", "data": {}}

This illustrates the envelope, not a specific endpoint response. Check the HTTP status and code; a nonzero business code can arrive with HTTP 200. The endpoint pages describe each data schema.

The reference describes the current backend implementation. Availability depends on its deployment to your environment. Contact support if the integration routes or account key controls are not yet enabled.

Choose your next step

Create a podcast

Create a script, prepare audio and render the workspace.

Prepare hosts and assets

Find voices and avatars, upload media and reuse templates.

Track tasks and outputs

Poll the correct task and retrieve generated media.

The OpenAPI specification contains every exposed operation. Each operationId is also its MCP tool name.