> ## Documentation Index
> Fetch the complete documentation index at: https://docs.particle.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Download the episode archive

> Downloads a month or a day of the podcast episode archive as gzip-compressed JSON Lines, one episode per line, ordered by publication time. Each line is the episode exactly as `GET /v1/podcasts/episodes/stream` delivers it with `include=all`. **Available by arrangement.** A day can be resumed with a Range request; a month cannot, so download days when your connection is unreliable. A download is a complete snapshot of its period: replace your copy rather than merging into it. Conditional requests with `If-None-Match` return 304 when nothing changed.



## OpenAPI

````yaml /openapi.json get /v1/podcasts/episodes/archive/download
openapi: 3.1.0
info:
  contact:
    email: api@particle.pro
    name: Particle
    url: https://particle.pro
  description: >-
    Podcast API for transcripts, mentions and sponsorship data. 140,000+
    podcasts transcribed, diarized and speaker-identified within minutes of
    airing, about 28,000 episodes a day. Search transcripts by keyword or
    meaning, track brand and company mentions with alerts, pull sponsor and
    ad-read data and rankings. REST API plus an MCP server for AI agents. Also
    company, people and topic intelligence.
  summary: >-
    Podcast API: transcripts, mentions, sponsors and rankings for 140,000+
    podcasts.
  termsOfService: https://particle.pro/legal/tos-api
  title: Particle API
  version: 0.1.0
  x-guidance: >-
    Podcast, people, company and topic intelligence. Authenticate with a pp_ API
    key (X-API-Key header) or pay per request with x402: a keyless call to a
    billable endpoint returns 402 with the payment requirements in the
    PAYMENT-REQUIRED header; sign the USDC transfer and repeat the request with
    PAYMENT-SIGNATURE. Start with GET /v1/podcasts/search?q=<show name>; the
    slugs in responses are the inputs to the other endpoints. Docs:
    https://docs.particle.pro; setup playbook:
    https://api.particle.pro/agents.md; endpoint and tool map with prices:
    https://api.particle.pro/llms.txt; credential recipe:
    https://api.particle.pro/auth.md.
  x-logo:
    url: https://particle.pro/favicon.svg
servers:
  - url: https://api.particle.pro
security:
  - ApiKeyHeader: []
  - BearerAuth: []
externalDocs:
  url: https://docs.particle.pro
paths:
  /v1/podcasts/episodes/archive/download:
    get:
      tags:
        - Podcast Episodes
        - tier:standard
      summary: Download the episode archive
      description: >-
        Downloads a month or a day of the podcast episode archive as
        gzip-compressed JSON Lines, one episode per line, ordered by publication
        time. Each line is the episode exactly as `GET
        /v1/podcasts/episodes/stream` delivers it with `include=all`.
        **Available by arrangement.** A day can be resumed with a Range request;
        a month cannot, so download days when your connection is unreliable. A
        download is a complete snapshot of its period: replace your copy rather
        than merging into it. Conditional requests with `If-None-Match` return
        304 when nothing changed.
      operationId: download-episode-archive
      parameters:
        - description: A month (YYYY-MM) or a day (YYYY-MM-DD), by UTC publication date.
          explode: false
          in: query
          name: period
          required: true
          schema:
            description: A month (YYYY-MM) or a day (YYYY-MM-DD), by UTC publication date.
            examples:
              - 2026-09
            pattern: ^\d{4}-\d{2}(-\d{2})?$
            type: string
        - description: >-
            Heavy relations to keep in each episode. Defaults to all of them.
            Narrowing it costs nothing to you but is served more slowly, and a
            narrowed download cannot be resumed with Range.
          explode: false
          in: query
          name: include
          schema:
            description: >-
              Heavy relations to keep in each episode. Defaults to all of them.
              Narrowing it costs nothing to you but is served more slowly, and a
              narrowed download cannot be resumed with Range.
            items:
              enum:
                - transcript
                - segments
                - clips
                - all
              type: string
            type:
              - array
              - 'null'
      responses:
        '200':
          content:
            application/gzip:
              schema:
                contentMediaType: application/octet-stream
                format: binary
                type: string
          description: The file.
        '206':
          content:
            application/gzip:
              schema:
                contentMediaType: application/octet-stream
                format: binary
                type: string
          description: The requested byte range of the file, answering a Range request.
        '304':
          description: 'Not modified: the If-None-Match tag still matches. No body.'
        '416':
          description: The requested range lies outside the file.
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/PlatformError'
          description: Error
      x-codeSamples:
        - label: cURL
          lang: curl
          source: |-
            curl -H "X-API-Key: $PARTICLE_API_KEY" \
              "https://api.particle.pro/v1/podcasts/episodes/archive/download?period=2026-09"
components:
  schemas:
    PlatformError:
      additionalProperties: false
      properties:
        detail:
          description: >-
            A human-readable explanation specific to this occurrence of the
            problem.
          examples:
            - Property foo is required but is missing.
          type: string
        error_code:
          type: string
        errors:
          description: Optional list of individual error details
          items:
            $ref: '#/components/schemas/ErrorDetail'
          type:
            - array
            - 'null'
        instance:
          description: >-
            A URI reference that identifies the specific occurrence of the
            problem.
          examples:
            - https://example.com/error-log/abc123
          format: uri
          type: string
        resolve:
          $ref: '#/components/schemas/ErrorResolve'
        status:
          description: HTTP status code
          examples:
            - 400
          format: int64
          type: integer
        title:
          description: >-
            A short, human-readable summary of the problem type. This value
            should not change between occurrences of the error.
          examples:
            - Bad Request
          type: string
        type:
          default: about:blank
          description: A URI reference to human-readable documentation for the error.
          examples:
            - https://example.com/errors/example
          format: uri
          type: string
      type: object
    ErrorDetail:
      additionalProperties: false
      properties:
        location:
          description: >-
            Where the error occurred, e.g. 'body.items[3].tags' or
            'path.thing-id'
          type: string
        message:
          description: Error message text
          type: string
        value:
          description: The value at the given location
      type: object
    ErrorResolve:
      additionalProperties: false
      properties:
        action:
          type: string
        endpoint:
          type: string
        message:
          type: string
        method:
          type: string
        url:
          type: string
      required:
        - message
      type: object
  securitySchemes:
    ApiKeyHeader:
      description: Pass your API key in the X-API-Key header (recommended).
      in: header
      name: X-API-Key
      type: apiKey
    BearerAuth:
      description: Pass your API key as a Bearer token in the Authorization header.
      scheme: bearer
      type: http

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.