Every new episode from your shows, pushed to your server
Choose the shows and give Podzone a URL. Every new episode is sent to your server as it’s transcribed, along with its sponsors, hosts, guests and topics.
How it works
-
1
Choose your shows
Pick them in the app or through the API, from the over 75,000 shows Podzone follows. On Business, send every show, or whole categories.
-
2
Give it a URL
An https endpoint on your server, and a secret to check that each batch came from Podzone.
-
3
New episodes arrive
Each one as it’s transcribed, and again once its sponsors, people and topics are known, in batches of up to 100.
-
4
Your server answers
Reply with a 200 and the next batch follows. Until you do, nothing after it is sent, so nothing is skipped.
What arrives for each episode
A batch carries up to 100 events, oldest first.
- When it’s transcribed: the episode as the API returns it, with its title, show notes, publication date, length, audio link and show.
- When it's enriched: the same episode with its sponsors and each ad read’s times and offer code, its hosts and guests, and what it’s about.
- The transcript, a link away. Each event links to the full transcript, as JSON with timestamps, text, SRT or VTT, for you to fetch with your API key when you want it.
Built to be relied on
Signed
Every batch is signed to the Standard Webhooks specification, so you can prove it came from Podzone, with libraries in most languages.
In order, nothing skipped
One batch at a time, oldest first. A batch your server doesn’t accept is sent again, and nothing after it goes out until it’s accepted.
Waits for you
If your server stays down, Podzone keeps trying for about a day, then switches the firehose off and emails your account’s admins. Switch it back on and it carries on where it stopped.
Replays
Send the last seven days again, in order: to fill a new receiver, or to recover from a bug in yours.
Test batches
Send a signed sample batch to your server, or to a tunnel on your laptop, before the real ones arrive.
Duplicates are easy to drop
An event can arrive twice, after a replay or a retry. Its id never changes, so drop the ones you’ve already stored.
See every batch it sends
The app’s Firehose page shows whether it’s on, its last batch and how your server answered, and a log of every batch. Send a test, send the last few days again, retry now or replace the secret from the same page.
Or do all of it from your own code: a firehose is a resource in the API, with the same key as everything else.
Example firehose
https://your-app.example.com/podzone/firehose
On Last batch 2 minutes ago: Delivered 6 events (HTTP 200)
Recent batches
| When | Result | Attempts |
|---|---|---|
| 13 Nov at 09:37 | Delivered 6 events (HTTP 200) | 1 |
| 13 Nov at 09:36 | Delivered 4 events (HTTP 200) | 1 |
| 13 Nov at 09:35 | Delivered 9 events (HTTP 200) | 2 |
| 13 Nov at 09:12 Test | Delivered 2 events (HTTP 200) | 1 |
Firehose, alerts or the API?
The firehose
Everything new from the shows you choose, as it happens: to keep your own copy, feed your own product or run your own analysis. For transcripts in bulk, Business adds daily export files.
Alerts
Only the episodes that mention your words, or that carry the sponsors, people and topics you follow, from every show. More on alerts.
The API
Ask when you need to: search what was said, read any episode’s transcript, and fill in what came before your firehose. More on the API.
Questions
Which plans include the firehose?
Pro, for the shows you choose, and Business, for every show or whole categories, with one firehose for each team. See the plans for how many shows.
Are transcripts included?
Each event links to its episode’s transcript rather than carrying it, so batches stay small. Fetch the ones you want with your API key: each is one of your plan’s transcript downloads and one API request. The batches themselves count against nothing.
What happens when my server is down?
The batch it missed is sent again for about a day, and nothing after it goes out meanwhile. If it still isn’t accepted, the firehose is switched off and your account’s admins are emailed. Switch it back on within seven days and it sends everything it held back, in order.
Can I receive older episodes?
A new firehose starts with the next new episode, and a replay sends the last seven days. For anything older, list a show’s episodes through the API. Replays and gaps.
Can the same episode arrive twice?
Yes, after a replay or a retry. Each event keeps its id, so drop the ones you’ve already stored.
What may I do with the data?
Build on it: use it in your business and in the products you build for your customers. Reselling it is not allowed, and training models on it needs a separate licence; the Terms of Service say exactly what is allowed.
For developers
- Firehose Receive every new episode from your chosen shows as signed batches, in order: the payload, retries, replays and testing.
- Bulk exports Download each day's new episodes, transcripts and shows as Parquet and JSONL.gz, and load them with DuckDB, BigQuery, pandas or your own tools.
- Webhooks Receive every alert match as a signed POST: the payload, verifying the signature, retries and testing.
- API reference Every endpoint, field and error.
Related
Start free, and upgrade when you need more.
Every plan includes alerts, search, transcripts, sponsors, people, topics, the API and the MCP server for AI agents. See the plans.
Start free