---
title: "Get podcast advertising profile"
method: GET
path: "/v1/podcasts/{id}/advertising"
tags: ["Podcasts", "tier:premium"]
---

# Get podcast advertising profile

`GET /v1/podcasts/{id}/advertising`

## Request

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

Returns advertising intelligence for a specific podcast, including aggregate stats, read type breakdown, and top sponsors. Identify the podcast by slug (e.g., 'all-in') or ID.

## Path parameters

- `id` string, required: Podcast slug (e.g., 'all-in'), internal ID, or numeric iTunes ID

## Response `200`

OK

- PodcastAdvertisingProfile
  - `avg_ads_per_episode` number, double, required: Average ads per episode
  - `episodes_with_ads` integer, required: Number of episodes containing ads
  - `podcast_id` string, required: Podcast identifier
  - `podcast_slug` string: Human-readable slug (when available)
  - `read_type_breakdown` ReadTypeBreakdown, required
    - `host_read` integer, required: Number of host-read ads
    - `pre_recorded` integer, required: Number of pre-recorded ads
  - `top_sponsors` TopSponsorEntry[], nullable, required: Most frequent sponsors
    - `ad_count` integer, required: Total number of ads
    - `company_id` string: Linked company identifier (domain, slug, or encoded ID)
    - `episode_count` integer, required: Number of episodes with ads from this sponsor
    - `slug` string: Stable human-readable handle (the linked knowledge-graph slug, e.g. 'nvidia'), when known. Prefer it (or company_id) as a /v1/companies key.
    - `sponsor_id` string: Linked sponsor ID, when known. Works as the {id} of /v1/podcasts/advertising/sponsors/{id} and its sub-resources, including when the sponsor has no linked company.
    - `sponsor_name` string, required: Sponsor name
  - `total_ads` integer, required: Total number of ads detected
  - `unique_sponsors` integer, required: Number of distinct sponsors

## 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)