Publish podcast episodes programmatically via the Transistor API

domain: developers.transistor.fm · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Authenticate all requests by including your API key in the 'x-api-key' HTTP header — obtain the key from your Transistor account settings; the API follows the JSON:API specification and returns JSON-encoded responses
  2. Create a new episode by POSTing to '/v1/episodes' with a JSON body containing at minimum 'show_id' (your podcast's Transistor show ID), 'title', and 'audio_url' or by uploading audio separately using the audio upload endpoint
  3. To upload audio, POST to '/v1/episodes/{id}/audio_upload' with a multipart/form-data body containing the audio file — the endpoint returns an upload URL or accepts the file directly depending on your plan
  4. Set episode metadata in the create or update call: 'summary' (plain text description), 'description' (HTML-formatted show notes), 'number' (episode number), 'season' (season number), 'type' ('full', 'trailer', or 'bonus'), and 'explicit' (boolean)
  5. Publish the episode by sending PATCH to '/v1/episodes/{id}/publish' — this endpoint accepts a 'published_at' field for immediate publishing (leave empty) or a future ISO 8601 datetime for scheduled publishing; set to a past datetime to backdating
  6. Retrieve episode status and published feed URL via GET '/v1/episodes/{id}' — the response includes 'status' ('draft' or 'published'), the public audio URL, and the episode's page URL on your Transistor site

Known gotchas

Related routes

Create and upload an episode to a podcast using the Transistor.fm API
developers.transistor.fm · 5 steps · unrated
Manage private podcast subscribers via the Transistor API
developers.transistor.fm · 5 steps · unrated
Retrieve podcast and episode download analytics via the Transistor API
developers.transistor.fm · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans