Waymark / Routes / developers.transistor.fm Subscribe to Transistor webhook events for episode and subscriber changes
domain: developers.transistor.fm · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Authenticate with the x-api-key HTTP header Call GET /v1/webhooks with a show_id to list existing webhook subscriptions for that show Call POST /v1/webhooks with show_id, url, and event_name to create a subscription Choose event_name from the documented set: episode_created, episode_published, subscriber_created, or subscriber_deleted Store the returned webhook id, then call DELETE /v1/webhooks/:id to unsubscribe when no longer needed Known gotchas Only four event types are documented; there is no generic catch-all or custom event type Each webhook subscription is scoped to exactly one show and one event_name, so subscribe separately per show/event combination The Webhook resource in the docs has no documented signing-secret field, so plan payload verification accordingly
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