Podcast API
Podcasts, episodes and full transcripts as JSON
Podcasts, their episodes and full transcripts with timestamped segments and identified speakers, linked by stable IDs and available to sync daily.
featured in
The Subalytics Podcast API returns the podcasts your key includes, their episodes, and a transcript for every episode it lists, as read-only JSON over HTTPS.
Podcasts, episodes and transcripts are linked by stable public IDs: a podcast's sub_id (10 hex characters) and an episode's episode_sub_id (16 hex characters). They never change, so they are safe to store as foreign keys.
New episodes are transcribed daily and usually appear within a few hours. Records are returned newest-added first, and date filters let you fetch only what changed since your last sync.
For what the data contains and who uses it, see podcast transcript data.
Endpoints for podcast data
Each endpoint links to its full reference in the API documentation.
Podcasts
/api/v1/podcasts/
The podcasts your key includes: name, feed details, categories, language, artwork, website and the publish date of the newest episode. Filter by sub_id, language, category or newest-episode date.
Podcast episodes
/api/v1/podcast-episodes/
Episodes published since Subalytics started tracking each podcast, and only those with a transcript. Filter by podcast, episode, publish date or when the episode became available (for sync).
Podcast transcripts
/api/v1/podcast-transcripts/
Transcript summaries by default; full=true adds speakers and timestamped segments. With full=true, limit defaults to 10 (maximum 10), since a full transcript can be 1–2 MB.
Podcast episodes with company mentions
/api/v1/entity-podcast-episodes/
Episodes that mention at least one monitored public company, with the transcript passage, timestamps and speaker of each mention. Part of the separate Entity Mentions product, with its own access.
Full transcripts with speakers and timestamps
Add full=true to get the complete transcript. Each segment has start and end times in seconds from the start of the audio, its text, and a speaker label that is a key into speakers. Labels are per transcript: SPEAKER_00 in one episode is unrelated to SPEAKER_00 in another.
Speaker identification is automatic and best-effort: any of name, role, title and company may be null, and role is the speaker's part in the conversation (host, co-host, guest). A transcript can change after it is first published, for example when speaker names are filled in later; its updated_at changes so a sync picks it up again.
GET /api/v1/podcast-transcripts/?episode_sub_id=c41f7a09e2b85d13&full=true
{
"episode_sub_id": "c41f7a09e2b85d13",
"podcast": { "sub_id": "a1b2c3d4e5", "podcast_name": "Example Business Show" },
"episode": {
"episode_sub_id": "c41f7a09e2b85d13",
"episode_title": "Rate Cuts, Robotaxis and the Week in Markets",
"published_at": "2026-09-24T16:38:09Z",
"audio_url": "https://media.example.com/c41f7a09e2b85d13.mp3",
"link": "https://podcasts.example.com/episodes/c41f7a09e2b85d13",
"image_url": "https://images.example.com/c41f7a09e2b85d13.jpg"
},
"language": "en",
"duration_seconds": 6875.2,
"speakers_identified": true,
"speakers": {
"SPEAKER_00": { "name": "Jane Host", "role": "host", "title": "journalist", "company": "Example Media" },
"SPEAKER_01": { "name": "Sam Guest", "role": "guest", "title": "economist", "company": null }
},
"segments": [
{ "start": 1.0, "end": 9.72, "text": "Welcome back to the show. Big week in markets.", "speaker": "SPEAKER_00" },
{ "start": 10.1, "end": 17.4, "text": "It really was. Let's start with the rate decision.", "speaker": "SPEAKER_01" }
],
"created_at": "2026-09-25T06:12:47Z",
"updated_at": "2026-09-27T05:48:31Z"
}
Transcript response fields
| Field | Type | Description |
|---|---|---|
episode_sub_id | string | The episode this transcript belongs to |
podcast | object | {sub_id, podcast_name} |
episode | object | {episode_sub_id, episode_title, published_at, audio_url, link, image_url}; the episodes endpoint is the source of truth |
language | string | null | Language detected from the audio, e.g. en |
duration_seconds | number | null | Measured audio length |
speakers_identified | boolean | false = speaker names haven't been identified (yet); labels still work, names are null |
created_at | date | When the transcript was first produced |
updated_at | date | Last change (re-transcription or speakers identified) |
speakers | object | full=true only. Speaker label → {name, role, title, company} |
segments | array | full=true only. {start, end, text, speaker} in order; start/end in seconds |
Daily sync
New or changed transcripts
GET /api/v1/podcast-transcripts/?updated_from=<last sync> returns summaries of transcripts that are new, re-transcribed or had speaker names filled in. Fetch the ones you need with ?episode_sub_id=<id>&full=true.
Newly available episodes
GET /api/v1/podcast-episodes/?transcribed_from=<last sync> filters on when an episode became available, so an episode published three days ago but transcribed today is included.
New podcasts
Re-list /api/v1/podcasts/ occasionally to pick up newly added podcasts. Start each *_from a few minutes before your previous sync; receiving the same record twice is harmless.
Date filters
Podcast date filters come in <name>_from / <name>_to pairs, named after the field they filter. Dates are UTC, in the format YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS, and both bounds are inclusive: a date-only *_to runs to the end of that day.
Responses return dates as ISO 8601 UTC with a Z suffix, e.g. 2026-09-25T05:00:00Z, the same format the filters accept, so a timestamp from the API can be used as either bound.
| Parameters | Endpoint | Field |
|---|---|---|
latest_episode_from / _to | podcasts | latest_published_episode_utc |
published_from / _to | podcast-episodes | published_utc |
transcribed_from / _to | podcast-episodes | transcribed_at |
updated_from / _to | podcast-transcripts | updated_at |
Responses and errors
Every endpoint returns the same JSON envelope, newest-added records first. Pass next_cursor back as cursor to get the next page, and stop when it is null. Podcast endpoints return only the podcasts your key includes; requesting any other podcast by sub_id, or one of its episodes by episode_sub_id, returns 403.
| Code | Meaning | When |
|---|---|---|
400 | Bad request | Unknown query parameter, invalid date or date range, invalid limit or invalid cursor. The message says which. |
401 | Unauthorized | Missing API key, or the key is not enabled for this endpoint. |
403 | Forbidden | The request names a podcast (or one of its episodes) that your key does not include. |
500 | Server error | Something went wrong on our side. Retry later. |
{
"success": true,
"results": [ ... ],
"returned_results": 25,
"limit": 25,
"next_cursor": "6a7d976dc8173839e225382f"
}
FAQ
Common questions
Episodes published since Subalytics started tracking each podcast; this is not the podcast's full back catalogue. Only episodes with a transcript are returned, and every episode listed has a transcript.
New episodes are transcribed daily and usually appear within a few hours of 05:00 UTC. Some take longer, and a few may never appear, for example if the audio is unavailable.
Yes, automatically and best-effort. Each segment has a speaker label, and speakers maps each label to name, role, title and company, any of which may be null. speakers_identified is false until names have been identified.
A full transcript can be 1–2 MB, so with full=true limit defaults to 10 and the maximum is 10. Without full=true you get summaries, which are cheap to page through to find what's new.
Send your API key in the X-API-key header with every request. Each key is enabled for specific endpoints; a request without a valid key, or to an endpoint your key isn't enabled for, returns 401.
JSON over HTTPS. All endpoints use GET, filter with query parameters and return the same response envelope: success, results, returned_results, limit, and next_cursor or offset. Endpoint paths end with a trailing slash.
Any query parameter not listed for an endpoint is rejected with 400 and a message naming it, e.g. "Unknown parameters: bad_param", so typos don't silently return the wrong data.
Yes. A machine-readable OpenAPI 3.1 description of every documented endpoint is at https://subalytics.com/openapi.json, for API clients, code generators and AI tools.
Contact us
Have a question or a custom use case?
Tell us what you're trying to monitor or search across, and we'll get back to you within a business day.
Get access to the Podcast API
Tell us which data you need and we'll enable the matching endpoints on your API key. The full reference, with every parameter and response field, is in the API documentation.