publisher object on the podcast detail response (GET /v1/podcasts/{id}), so you usually don’t need a separate lookup to display a podcast’s publisher — these endpoints exist for browsing and reverse navigation.
Use these endpoints when you want to:
- Build a “browse by publisher” view of the catalog.
- Resolve a publisher slug from a URL into its podcasts.
- Rank publishers by catalog size, or list them alphabetically.
- Cross-reference a podcast’s publisher with the rest of its catalog.
Identifying a publisher
Every publisher endpoint that takes an{id} path parameter accepts either form:
- Slug (recommended): a stable, human-readable identifier —
goalhanger,iheartpodcasts,bbc-radio-4. Slugs are populated for the vast majority of publishers and returned on every publisher response. - ID: the publisher ID. Always works as a fallback for the small number of publishers whose name doesn’t slugify (e.g. names that aren’t representable as ASCII URL slugs).
List publishers
Response (truncated)
Query parameters
Get a publisher
Response
List podcasts for a publisher
Pivot from a publisher to its full catalog, ordered by popularity:Response (truncated)
Podcast objects returned by GET /v1/podcasts — see the podcasts overview for the full field reference.
Anatomy of a publisher
The same publisher also appears in compact form (
id, slug, name only) as the publisher field on the podcast detail response — you do not need a separate publisher lookup just to display a podcast’s publisher in the UI.
Choosing the right endpoint
Related
- Publisher advertising — roll up ads, sponsors, and bundle-buy intelligence across a publisher’s full catalog.
- Podcasts overview — full Podcast object and other sub-resources.
- Episodes — drill from a podcast into its individual episodes.
- External links — third-party platform presences for a podcast.