Developer guide

EDGAR API for Developers

A developer-focused guide for teams searching EDGAR API examples, tutorials, and Python usage before deciding between direct SEC.gov access and a normalized filing API.

Subscribe on RapidAPI Try demo JSON View pricing

GET /v1/sec/companies/search?q=apple&limit=10

{
  "data": [
    {
      "changeType": "material_event",
      "observedAt": "2026-07-02T17:23:22+00:00",
      "filing": {
        "ticker": "MSFT",
        "form": "8-K",
        "eventType": "current_report",
        "filedAt": "2026-07-02"
      }
    }
  ],
  "meta": { "count": 1 }
}

Use SEC Event Intelligence When

The buyer workflow needs a stable API response for polling, filtering, and downstream automation.

Developers who need JSON responses for scheduled jobs, dashboards, or agents.
Teams that want ticker, CIK, company lookup, watchlist, and filing-change endpoints.
Apps where parsing raw submissions is not the core product work.

Use The Alternative When

A simpler public source, raw document workflow, or human-readable alert fits the job better.

Research projects that need complete raw filings, exhibits, and attachments.
Teams that want to implement their own EDGAR crawler, cache, and parser.
Workflows that need unsupported forms or specialized extraction beyond filing metadata.

Decision rule. Use direct EDGAR access when source-document control matters most. Use SEC Event Intelligence when the developer task is connecting filing metadata to software quickly.