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

# A company that files with the SEC, as SEC's own list names it, and whether the team can ask for its filings

> A company that files with the SEC, by its ticker or its SEC number, before you add it: SEC's own name, number and exchange for it; the company PodData holds for it, when your team may see that company; whether asking for its filings here counts toward your plan's filers a day; and, for one your team sees, where reading its last year of filings stands.

**Before:** Nothing.

**Next:** Add it with `POST /targets` and its `ticker` or `cik`. PodData then reads its filings, first on the reader’s next run.

**Limits:** A ticker or number SEC's list doesn't hold is a `404`. Asking counts only for a filer PodData doesn't read yet: 1 on Free, 5 on Pro and Pilot, and 25 on Enterprise a UTC day.

**MCP tool:** `find_filer`, on PodData's MCP server at `https://api.poddata.ai/mcp`, does what this route does, with the same key. See [The MCP server](https://docs.poddata.ai/mcp.md).


## OpenAPI

````yaml /openapi.json get /filers/{filer}
openapi: 3.1.0
info:
  title: PodData API
  version: 1.0.0
  description: >-
    PodData is competitive intelligence from the record: what leaders said on
    podcasts, in interviews and at their own events, as quotes with the speaker,
    the source, the day and the second; and, for a diligence, what public
    sources say about a company and its rivals, read through links a person on
    your team has confirmed.


    ## Quick start


    1. **A key.** Someone on your team makes one in the workspace, Settings ›
    API keys. Send it on every call as `Authorization: Bearer pd_live_…`. Keep
    it in an environment variable, such as `PODDATA_API_KEY`, and never print it
    or write it to a file.

    2. **A target.** `POST /targets` with a company's `name` and `domain`, an id
    from `GET /companies?q=`, or its SEC `ticker`.

    3. **Its links and rivals.** `POST /targets/{company}/find` and `POST
    /targets/{company}/rivals/find` propose them, each with the page that shows
    it. Show each one to a person, and confirm it only on their yes.

    4. **A read.** `POST /targets/{company}/read` with `{"rivals": true}` asks
    PodData to read the target and its confirmed rivals now. `GET
    /targets/{company}/coverage` says what has been read, source by source.

    5. **The files.** `GET /targets/{company}/folder` lists a file for each
    source, for the target and each confirmed rival. `?format=zip` is all of
    them at once.

    6. **A report.** `POST /diligence-reports` makes one with five empty pages.
    Write each with `PUT /diligence-reports/{id}/pages/{page}`, check it with
    `POST /diligence-reports/{id}/check`, and read it with every figure filled
    with `GET /diligence-reports/{id}`. Or have PodData's own agent write it,
    `POST /diligence-reports/{id}/runs`, and follow the run with `GET
    /diligence-runs/{id}`.


    The tags below are in that order. Each operation says what has to be true
    first, what to call next and its limits, with a made-up example of the call
    and its answer.


    **For an assistant,** start from `https://api.poddata.ai/llms.txt`, which
    needs no key: the same steps, the MCP server, and PodData's diligence skill
    with its puller, which saves a target's folder, its rivals' and its reports
    to disk. The MCP server does what the API does:
    `https://api.poddata.ai/mcp`, with the same key or by signing in to PodData,
    and each operation here names its tool in `x-mcp-tool`. To add it to Claude
    Code with the key read from the environment each time it starts, never
    written down, run this as it is, in single quotes: `claude mcp add
    --transport http --scope project poddata https://api.poddata.ai/mcp --header
    'Authorization: Bearer ${PODDATA_API_KEY}'`.


    **Limits.** 120 requests a minute a key, then a `429` with `Retry-After`. A
    team's plan sets how many reads, rival finds and filers it may ask for a
    day, and a call past one is a `403` with the code `plan` that says the
    limit. A list or a file holds at most 80 words in a row of a source's own
    text; a whole document or transcript comes from its own route, one at a
    time, under a daily limit.


    **Errors** are `{"error": {"code": "…", "message": "…"}}`, the message a
    sentence that says what to do.
servers:
  - url: https://api.poddata.ai/v1
security:
  - key: []
tags:
  - name: Targets
    description: >-
      Start here. The companies your team looks at: add one by its name and
      domain, by an id from `GET /companies`, or by its SEC ticker. A target is
      your team's alone, and nothing says another team looks at it.
  - name: Links
    description: >-
      A target's own domain, listings and accounts. PodData proposes them from
      its own site, and reads only through a link a person on your team has
      confirmed.
  - name: Rivals
    description: >-
      The companies a target competes with. PodData finds and tests candidates
      and proposes only the rivals; a person confirms each, and then it is read
      beside the target.
  - name: Reads
    description: >-
      Ask PodData to read a target and its confirmed rivals now, and see what
      has been read for it, source by source, and what is missing and why.
  - name: Records and signals
    description: >-
      What PodData read about a company through its confirmed links: records,
      such as filings, licences, cases and stories, and signals, such as reviews
      and ratings, each with its own day and its page on the source's site. And
      the figures your team's own data licences read.
  - name: Ads and site
    description: >-
      A brand's ads in Meta's US ad library, from PodData's weekly reads, and
      the pages of a company's own site as PodData read them.
  - name: Number tools
    description: >-
      Figures computed on the server, so an assistant never pages through
      thousands of reviews or does the sums itself: ratings, complaints, a
      series, a timeline, ads and a site, for a company beside its confirmed
      rivals. Each answers the figures, the rows behind them, the evidence and
      how they were built.
  - name: Folder
    description: >-
      Everything PodData holds for a target and its confirmed rivals, as files:
      an index, a CSV a source and kind, and one zip.
  - name: Reports
    description: >-
      A diligence report: an overview and five pages, each figure filled by a
      number tool when the report is read, and a check that refuses what the
      evidence doesn't hold. Your own assistant writes it a page at a time, or
      PodData's agent does.
  - name: Report runs
    description: >-
      PodData's own agent writing a report or changing one: each run's status,
      its turns and what it cost.
  - name: Quotes
    description: >-
      What people said, as quotes with the speaker, the show, the day, the
      second and a page to cite.
  - name: People
    description: >-
      The people PodData quotes, their sources and timelines, and lookups of
      someone new.
  - name: Shows and episodes
    description: The shows PodData reads and their episodes, with who spoke when.
  - name: Companies
    description: >-
      What companies said and filed themselves: their documents, events,
      transcripts, slides, posts and figures, and passages of at most 80 words
      from them.
  - name: Trackers
    description: >-
      A tracker follows a topic or a person and sends each new quote it matches
      by email, Slack or webhook.
  - name: Lists
    description: >-
      A team's own lists of people and companies, to narrow a search or a
      tracker to them.
  - name: Saved
    description: >-
      What a person signed in has saved, their saved filters and their calendar
      feed. A key, which has no person, is refused most of these.
  - name: Sources
    description: >-
      The sources PodData reads, what it holds from each, and how much of the
      watch list is covered.
  - name: Webhooks
    description: Webhooks a program registers to be sent what its trackers match.
  - name: Usage
    description: The team's calls and reads, counted by day and kind.
  - name: Help
    description: >-
      PodData's guide to itself: what each part of PodData does and where in the
      workspace it's done, topic by topic.
paths:
  /filers/{filer}:
    get:
      tags:
        - Targets
      summary: >-
        A company that files with the SEC, as SEC's own list names it, and
        whether the team can ask for its filings
      description: >-
        A company that files with the SEC, by its ticker or its SEC number,
        before you add it: SEC's own name, number and exchange for it; the
        company PodData holds for it, when your team may see that company;
        whether asking for its filings here counts toward your plan's filers a
        day; and, for one your team sees, where reading its last year of filings
        stands.


        **Before:** Nothing.


        **Next:** Add it with `POST /targets` and its `ticker` or `cik`. PodData
        then reads its filings, first on the reader’s next run.


        **Limits:** A ticker or number SEC's list doesn't hold is a `404`.
        Asking counts only for a filer PodData doesn't read yet: 1 on Free, 5 on
        Pro and Pilot, and 25 on Enterprise a UTC day.
      operationId: findFiler
      parameters:
        - schema:
            type: string
            minLength: 1
            maxLength: 20
            description: >-
              A ticker, HIMS or NYSE:HIMS, or an SEC number with or without its
              leading zeros
          required: true
          description: >-
            A ticker, HIMS or NYSE:HIMS, or an SEC number with or without its
            leading zeros
          name: filer
          in: path
      responses:
        '200':
          description: >-
            The filer, the company PodData holds for it if the team may see it,
            and what asking for it would do
          content:
            application/json:
              examples:
                made-up:
                  summary: 'Made up: no team’s data'
                  value:
                    ticker: NWDL
                    cik: '0009999901'
                    name: NORTHWIND DENTAL HOLDINGS INC
                    exchange: NYSE
                    read_on: '2026-11-17'
                    company: null
                    asking: open
                    counts: true
                    asked_today: 0
                    limit: 5
                    filings: null
              schema:
                type: object
                properties:
                  ticker:
                    type: string
                  cik:
                    type: string
                  name:
                    type: string
                  exchange:
                    type:
                      - string
                      - 'null'
                  read_on:
                    type: string
                  company:
                    type:
                      - object
                      - 'null'
                    properties:
                      id:
                        type: string
                      name:
                        type: string
                      by_request:
                        type: boolean
                    required:
                      - id
                      - name
                      - by_request
                  asking:
                    type: string
                    enum:
                      - open
                      - not_here
                  counts:
                    type: boolean
                  asked_today:
                    type: integer
                  limit:
                    type:
                      - integer
                      - 'null'
                  filings:
                    type:
                      - object
                      - 'null'
                    properties:
                      state:
                        type: string
                        enum:
                          - reading
                          - read
                          - not_read_here
                      asked_at:
                        type:
                          - string
                          - 'null'
                      listed:
                        type: integer
                      parsed:
                        type: integer
                    required:
                      - state
                      - asked_at
                      - listed
                      - parsed
                required:
                  - ticker
                  - cik
                  - name
                  - exchange
                  - read_on
                  - company
                  - asking
                  - counts
                  - asked_today
                  - limit
                  - filings
        default:
          description: An error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
      x-codeSamples:
        - lang: bash
          label: curl, made-up values
          source: |-
            curl 'https://api.poddata.ai/v1/filers/NYSE:NWDL' \
              -H "Authorization: Bearer $PODDATA_API_KEY"
components:
  schemas:
    ApiError:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              enum:
                - bad_request
                - no_key
                - plan
                - forbidden
                - not_found
                - conflict
                - unclear
                - slow_down
                - internal
            message:
              type: string
          required:
            - code
            - message
      required:
        - error
  securitySchemes:
    key:
      type: http
      scheme: bearer
      description: >-
        An API key, sent as `Authorization: Bearer pd_live_…`. Someone on your
        team makes one in the workspace, Settings › API keys; it's shown once.
        Staging's keys start with `pd_test_`.

````

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