Skip to main content
Most podcast APIs give you metadata — titles, descriptions, RSS feeds. Particle API gives you what’s in the audio. Every episode is transcribed and diarized, broken into structural segments (intros, ads, topic discussions, interviews), distilled into engagement-scored clips, and linked to a knowledge graph of speakers, entities, and topics. The shows themselves are scored for political bias with structured evidence.

What you can build

  • Entity tracking — Find every episode, segment, and dialogue line where a person or company is discussed.
  • Highlight reels — Pull engagement-scored clips with ready-to-share intro_statement copy and direct MP3 URLs.
  • Sponsor analytics — See which podcasts a competitor advertises on, who co-sponsors with whom, and host-read vs pre-recorded breakdowns.
  • Research tools — Search transcripts with timestamps, exports as JSON or SRT, scoped by speaker or time range.
  • Bias analysis — Audit a show’s leaning with structured transcript_evidence and web_research_evidence.

Resource hierarchy

Every resource is reachable both scoped to its parent (e.g., segments for a specific episode) and across the catalog (e.g., all segments matching a filter). Heavier endpoints — full transcripts, transcript mentions, cross-catalog segments and clip search, and advertising analytics — are priced higher per call than light metadata lookups; see Concepts → Pricing weight.

Episodes

Cross-podcast discovery, filtering, and per-episode sub-resources.

Guests

The people who appear on shows — lifetime profiles, appearances, trending press tours, and brand-suitability exposure.

Format profile

What kind of show it is — guest frequency, interview/panel/call-in/solo formats, ads, video, episode length, and cadence — all filterable.

Transcripts

Diarized dialogue, word-level timestamps, SRT export, and entity mentions in context.

Segments & clips

AI-identified structural sections and engagement-scored highlight moments.

Advertising

Sponsors, leaderboards, co-occurrence, and per-company ad presence.

External links

Every directory, social profile, video channel, and website the podcast lives on — with resolved URLs and audience metrics.

Lookup by external ID

Reverse the external-links index: resolve Apple, Spotify, YouTube, and other platform identifiers to Particle podcasts in bulk.

Publishers

Browse the organizations behind the catalog and pivot from a publisher to its full lineup of podcasts.

Ratings & reviews

User-generated 1–5 star ratings and review text, per-platform star histograms, and a periodic LLM-generated narrative summary of listener sentiment.

Get a podcast

Resolve by slug, canonical ID, or numeric Apple/iTunes collection ID:
Response from GET /v1/podcasts/pivot (truncated)
The speakers array is the recurring cast aggregated across episodes. Each entity_slug is a knowledge-graph handle you can pass to entities endpoints or to GET /v1/podcasts/episodes?entity_id=… to follow that speaker across the whole catalog.
Already have a platform-native ID? A numeric Apple/iTunes collection ID can be passed straight into the {id} slot — e.g. GET /v1/podcasts/1535809341 — no lookup needed. For a Spotify show ID, YouTube channel ID, RSS feed URL, or other platform identifier, use GET /v1/podcasts/lookup to deterministically resolve any of them (or up to 100 in a single call) to Particle podcasts.

Search by name

If you only know the show by name, use GET /v1/podcasts/search with a fuzzy q= query — it’s case-insensitive and matches title and description:
The response is a paginated list of compact podcast objects — same PageResponse<Podcast> envelope used by every list endpoint, ranked by match quality. (GET /v1/podcasts?q=… returns the same results and remains supported for backwards compatibility.) q= is a ranked text search, not a deterministic mapping: the top hit is usually right but isn’t guaranteed to be. If you need a deterministic answer keyed on a platform-native identifier (Apple, Spotify, YouTube, …), use GET /v1/podcasts/lookup instead.

Curate by popularity and topic

The list endpoint is also a discovery tool. Filter by topic_id, language, or suitability_tier, and narrow to the most popular shows with popularity_threshold. Currently-charting podcasts carry a popularity field — a global popularity percentile in (0,1] (a cume_dist ranking over every charting podcast, where 1.0 is the single most popular show). It is omitted for podcasts not currently on any chart. popularity_threshold filters on that same value (and, because non-charting podcasts have no percentile, excludes them whenever it is set):
This returns the top-quartile-popularity podcasts where fantasy football is a substantive share of the show — the topic_id filter requires the topic to carry at least 20% of a podcast’s episodes and ranks by topic concentration. popularity_threshold is always global: it ranks across all charting podcasts, never within topic_id or any other filter. Podcasts that aren’t currently charting have no percentile and are excluded whenever the filter is set, so a high threshold on a narrow topic can return nothing — lower or drop popularity_threshold to widen the set. This pairs naturally with the episode feed: curate a list here, then hand its podcast IDs to the feed as an explicit, stable podcast_ids set instead of the feed’s dynamic popularity stream.

Bias analysis

Every podcast carries a quick bias enum (LEANS_LEFT, LEANS_RIGHT, CENTER, MIXED, UNCLEAR) on the podcast resource. The bias endpoint returns the underlying analysis: structured reasoning, transcript-level evidence, web-research evidence, and the sample episodes that drove the conclusion.
Response (truncated)
Use the result for filtering or tagging; surface the reasoning and transcript_evidence fields when users want to know why.

Mentions across a podcast’s episodes

To find every episode of a single podcast where an entity comes up — without iterating episodes yourself — use the podcast-scoped mentions endpoint:
Response (truncated)
For the dialogue lines around each mention, drill into one episode with transcript mentions.

Choosing the right endpoint

The split between Episode search and Mentions is deliberate: Episode search ranks dialogue by relevance to a query (similarity, BM25, or hybrid). Mentions returns episodes containing a named entity, ordered by recency, with every dialogue line where that name appears. Different shapes for genuinely different questions — see the Episode search and Mentions pages for full guidance.
  • Search — find a podcast by name, with match_quality on every result
  • Episode search — find dialogue by topic or exact phrase (semantic, keyword, hybrid)
  • Mentions — every line where a person or company is named
  • Guests — the people who appear on shows, their appearances, trends, and suitability exposure
  • Format profile — guest frequency, detected formats, ads, video, episode length, and cadence as filterable attributes
  • Episodes — discovery, filtering, sub-resources
  • Transcripts — dialogue, words, mentions, SRT
  • Segments & clips — structural breakdown and highlight moments
  • Advertising — sponsor analytics
  • External links — directories, social profiles, websites with resolved URLs and audience metrics
  • Lookup by external ID — reverse the external-links index for Apple, Spotify, YouTube, and other platform identifiers
  • Publishers — browse organizations and pivot from a publisher to its catalog
  • Ratings & reviews — user-generated star ratings, review text, per-platform aggregates, and narrative sentiment summaries