Authenticate using token-based HTTP authentication: include the header 'Authorization: Token token=YOUR_API_TOKEN' on every request — obtain your podcast ID and API token from the Buzzsprout API settings page in your account
List all episodes for your podcast by sending GET to 'https://www.buzzsprout.com/api/{PODCAST_ID}/episodes.json' — the response is a JSON array of episode objects with fields including 'id', 'title', 'audio_url', 'published_at', and 'private'
Create a new episode by POSTing to 'https://www.buzzsprout.com/api/{PODCAST_ID}/episodes.json' with 'Content-Type: application/json; charset=utf-8' and a JSON body containing 'title', 'description' (HTML), 'audio_url' (URL of a publicly accessible audio file), and optionally 'published_at' (ISO 8601 datetime for scheduling) and 'private' (boolean)
Update an existing episode with PUT to 'https://www.buzzsprout.com/api/{PODCAST_ID}/episodes/{EPISODE_ID}.json' — include only the fields you want to change; all other fields retain their current values
Delete an episode by sending DELETE to 'https://www.buzzsprout.com/api/{PODCAST_ID}/episodes/{EPISODE_ID}.json' — deletion removes the episode from your feed and cannot be undone; the audio file hosted on Buzzsprout is also deleted
All API URLs end in '.json' to indicate JSON serialization — omitting the '.json' suffix will return an error
Known gotchas
Buzzsprout uses 'Token token=YOUR_API_TOKEN' (with 'Token' as the scheme and 'token=' as a prefix before the key value) — the formatting is non-standard and differs from typical 'Bearer' token authorization headers
The 'audio_url' field in the episode create/update payload must be a publicly accessible URL from which Buzzsprout can download and re-host the audio — Buzzsprout does not accept direct file uploads through the API
Buzzsprout does not provide a separate publish/unpublish endpoint — control visibility by setting 'private: true' for unpublished episodes or by setting 'published_at' to a future datetime for scheduled releases
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