---
title: "List entities in an episode"
method: GET
path: "/v1/podcasts/episodes/{id}/entities"
tags: ["Podcast Episodes", "tier:standard"]
---

# List entities in an episode

`GET /v1/podcasts/episodes/{id}/entities`

## Request

- Base URL: `https://api.particle.pro`
- URL: `https://api.particle.pro/v1/podcasts/episodes/{id}/entities`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Returns knowledge graph entities mentioned in a specific episode, with salience scores and occurrence counts.

## Path parameters

- `id` string, required: Episode slug or ID

## Query parameters

- `limit` integer: Results per page (default: all)
- `cursor` string: Opaque pagination cursor from previous response

## Response `200`

OK

- PageEpisodeEntityAppearance
  - `cursor` string: Pass to next request for more results
  - `data` EpisodeEntityAppearance[], nullable, required: List of results
    - `entity` EntityCompact, required
      - `company` EntityCompany
        - `domain` string: Company website domain
        - `id` string, required: Company identifier
        - `ticker` string: Primary stock ticker symbol
      - `description` string: Short description
      - `id` string, required: Entity ID
      - `image_url` string: Entity image URL
      - `name` string, required: Entity name
      - `person` EntityPerson
        - `company` string: Current company name
        - `id` string, required: Person identifier
        - `image_url` string: Person headshot URL
        - `title` string: Current role title
      - `slug` string, required: Human-readable slug identifier
      - `type` EntityType
        - `name` string, required: Human-friendly display label (e.g. 'Company').
        - `slug` string, required: Stable identifier, safe to pass to the type query parameter (e.g. 'company').
      - `wikipedia_url` string: Wikipedia URL
    - `occurrences` integer, required: Number of mentions in the episode
    - `salience` number, double, required: Importance score for the entity within the episode. When salience metadata is available, this is a percentile rank in (0.0, 1.0) — 0.95 means more salient than 95% of other entities mentioned, and the top entity approaches but never reaches 1.0. A value of 0.0 indicates the salience is unknown or unavailable.
  - `has_more` boolean, required: Whether more results exist

## Other responses

- `402`: Payment Required. Read error_code. payment_required is the x402 path: either a keyless request being challenged — pay $0.03 in USDC per request (requirements in the PAYMENT-REQUIRED header) or send a pp_ API key — or a supplied payment that failed settlement (details in the PAYMENT-RESPONSE header; retry the same signature before signing a new one). See https://docs.particle.pro/x402. Any other code means the credential was accepted but does not cover this request (a plan or session gate such as premium_required or paid_plan_confirmation_required); its resolve says how to obtain access, and no payment header is sent.
- `default`: Error

---

[API](https://skmtc.dev/particle/apis/particle-api.md) · [All operations](https://skmtc.dev/particle/apis/particle-api/llms.txt) · [OpenAPI document](https://skmtc.dev/particle/apis/particle-api/revisions/416ba82ab9d7?raw)