Reference · built on requestCommons signalEconomic & calendar reference

SEC EDGAR APIs

Company filing histories and XBRL financial facts from the SEC's EDGAR system, as JSON from data.sec.gov.

Request accessPricing ↗

About

EDGAR is the U.S. Securities and Exchange Commission's filing system. Companies, funds, and insiders file there, and the SEC republishes each filing free of charge. The EDGAR APIs on data.sec.gov return JSON: a filer's submission history and metadata from the submissions API, and XBRL financial facts through the companyconcept, companyfacts, and frames APIs. Two ZIP files, companyfacts.zip and submissions.zip, bundle the same data nightly.

On Fibric, an operator reads a counterparty's filing history and reported financials, checks them against the account or vendor in your own systems, and proposes a credit decision or a review for your approval.

This is a reference listing. It documents what Fibric would read from SEC EDGAR APIs and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Submissions API, data.sec.gov/submissions/CIK##########.json: filing history, current and former names, tickers, exchanges, and recent filings
  • Company Facts API, /api/xbrl/companyfacts/CIK##########.json: every XBRL concept a company has reported, in one response
  • Company Concept API, /api/xbrl/companyconcept/CIK##########/us-gaap/AccountsPayableCurrent.json: one concept for one filer, split by unit of measure
  • Frames API, /api/xbrl/frames/us-gaap/AccountsPayableCurrent/USD/CY2019Q1I.json: one fact across all filers for an annual, quarterly, or instantaneous period
  • Nightly companyfacts.zip and submissions.zip bulk files, refreshed around 3:00 a.m. ET
  • RSS feeds of latest filings, filterable by company, CIK, or form type, and daily and quarterly index files under /Archives/edgar/

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Check a new trade account against its filings

    When a customer applies for terms, the operator pulls the filer's submission history and latest reported balance sheet facts and attaches them to the application for the credit reviewer.

    With Account Application, Credit Hold

  • Prepare for a meeting with a listed customer

    Before a review with a listed customer or supplier, the operator reads the latest Form 10-K and 10-Q entries in the submissions history and the concepts in companyfacts, and drafts a one-page brief.

    With Meeting Prep

  • Place a peer set beside your own numbers

    Pull a Frames API series such as us-gaap AccountsPayableCurrent for one period across every filer and put your own figure beside the peer set in the board pack.

    With Board Pack

Requirements

  • A User-Agent header of the form "Sample Company Name AdminContact@sample-company.com" on every request
  • The 10-digit, zero-padded Central Index Key (CIK) of each filer you want to read
  • A request rate held under the SEC's fair-access ceiling of 10 requests per second across all your machines
Authentication
No key or account. Every request must declare a User-Agent header naming your company and a contact email, in the form the SEC gives on its Accessing EDGAR Data page.

Limits

  • The SEC limits each user to 10 requests per second, counted across all machines; excess traffic is rate-limited for a period
  • The APIs do not support CORS, so a browser cannot call data.sec.gov directly
  • The XBRL APIs return tagged facts from the us-gaap, ifrs-full, dei, and srt taxonomies, not the filing documents themselves
  • The SEC offers no technical support for scripted access and prohibits unclassified bots and crawlers

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request SEC EDGAR APIs ↗

Questions and answers

Do the EDGAR APIs need an API key?
No. The SEC says the APIs need no authentication or key. You must send a User-Agent header naming your company and a contact email, and stay under 10 requests per second. The SEC does not offer support for scripted access.
How fresh is the data?
The SEC states the submissions API updates with a typical delay under a second after a filing, and the XBRL APIs under a minute. Delays can grow at peak filing times. The bulk ZIPs refresh nightly around 3:00 a.m. ET.
Can I redistribute what I read from EDGAR?
The SEC's policy says information on sec.gov is public and may be copied or further distributed without permission. The SEC seal, logos, and the EDGAR name are registered marks and are excluded.
Ask about SEC EDGAR APIs

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by U.S. Securities and Exchange Commission (data.sec.gov, www.sec.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy