SEC EDGAR CompanyFacts API
Find SEC EDGAR CompanyFacts JSON paths like CIK0001018724, XBRL endpoints, fair-access rules, and DealCharts links from filings to structured-finance context.Developer and analyst entrypoint
Find the SEC CompanyFacts JSON. Keep the structured-finance context.
The SEC gives you public filing JSON, including CompanyFacts paths by CIK. DealCharts helps connect that source data to deals, funds, source documents, and facts endpoints you can cite.
CIK0001018724 CompanyFacts URL
What the SEC APIs Give You
The SEC's public developer documentation separates EDGAR data access from filer-submission APIs. For data analysis, the important public surfaces are submissions history and extracted XBRL facts served as JSON on
.data.sec.gov
Public JSON, no data API key
The SEC describes
as RESTful JSON APIs for submissions by company and extracted XBRL data. The SEC API page says these data APIs do not require authentication or API keys.data.sec.gov
Declared User-Agent and 10 requests per second
SEC guidance asks automated users to declare a User-Agent, download only what they need, and keep request rates within the current 10 requests per second fair-access limit.
Where DealCharts Adds Structure
Raw EDGAR is the source. DealCharts is the read layer for structured-finance context built from those public filings. Use it when the task is not just "fetch a filing," but "connect this filing, CIK, fund, deal, or chart to a citable structured-finance object."
Move from CIKs to deal and fund pages
Search resolves issuer names, fund names, deal slugs, BDC tickers, and structured-finance entities into stable DealCharts pages and facts paths.
Use facts JSON for agents and scripts
Facts files carry identifiers, dates, source documents, provenance, citation text, and page URLs for downstream research, retrieval, and audit trails.
Keep ontology and source documents visible
The ontology maps FilingDocument, Deal, Tranche, Fund, Counterparty, Chart, and Dataset objects so your application can distinguish source filings from DealCharts projections.
Route hard questions to CMD+RVL
If you need a custom monitor, bulk pull, or filing-state workflow, CMD+RVL can scope the data path without moving evidence logic into DealCharts.
Structured-Finance Workflows
- CIK to filing history
Find the filing universe first
Use SEC submissions JSON for a 10-digit CIK such as
. Then search DealCharts when you need structured-finance exposure, deal pages, or facts JSON tied to that filing entity.CIK0001018724 - 10-D and ABS surveillance
Connect remittance filings to deal objects
Use EDGAR for source filings. Use DealCharts to inspect CMBS and Auto ABS deal pages, chart paths, facts JSON, and source document references for normalized surveillance context.
- Fund holdings
Bridge NPORT-P disclosures into fund facts
Fund pages expose NPORT-P-derived holdings context and facts JSON, useful when a model or analyst needs a source-backed answer to who holds a structured-finance position.
- AI retrieval
Prefer citable facts over scraped snippets
Retrieval agents can pair
, facts endpoints, and ontology references with SEC source URLs to ground answers in public filings and stable DealCharts IDs.llms.txt
Endpoint Map
| Endpoint | Use it for | Source or layer |
|---|---|---|
https://data.sec.gov/submissions/CIK##########.json | Current filing history by 10-digit CIK, including recent filings and entity metadata. | SEC |
https://data.sec.gov/api/xbrl/companyfacts/CIK##########.json | All non-custom taxonomy XBRL concepts for a filing entity in one JSON call. | SEC |
https://data.sec.gov/api/xbrl/companyconcept/CIK##########/us-gaap/AccountsPayableCurrent.json | One XBRL concept for one company, grouped by unit of measure. | SEC |
https://dealcharts.org/.netlify/functions/search?query=blackrock | Resolve names, funds, BDCs, deals, and counterparties into DealCharts pages. | DealCharts |
https://dealcharts.org/llm/facts/{entity_key}.json | Machine-readable structured-finance facts with identifiers, dates, source links, and provenance. | DealCharts |
https://dealcharts.org/ontology/ | Entity and relationship model for deals, filings, tranches, funds, counterparties, charts, and datasets. | DealCharts |
Examples to Copy
# SEC submissions history for Amazon.com, Inc. from the search query patterncurl -H "User-Agent: Your Company name@example.com" \https://data.sec.gov/submissions/CIK0001018724.json# SEC CompanyFacts JSON for the same CIKcurl -H "User-Agent: Your Company name@example.com" \https://data.sec.gov/api/xbrl/companyfacts/CIK0001018724.json# Resolve a structured-finance name in DealChartscurl "https://dealcharts.org/.netlify/functions/search?query=blackrock"# Pull a DealCharts facts filecurl https://dealcharts.org/llm/facts/bmark2021-b28.json
Frequently Asked Questions
Is DealCharts a replacement for data.sec.gov
?
No.
is the SEC source for submissions history and XBRL data. DealCharts is useful after that first fetch, when you need the structured-finance layer: deal pages, fund exposure, facts JSON, source links, ontology, and datasets.data.sec.gov
Does SEC EDGAR API access require an API key?
The public SEC data APIs on
do not require authentication or API keys, according to the SEC API documentation. Automated access still has fair-access duties: declare a User-Agent, moderate requests, and download only what you need.data.sec.gov
Where do I find SEC CompanyFacts JSON for CIK0001018724
?
is Amazon.com, Inc. The SEC endpoint isCIK0001018724
. DealCharts helps when you need to connect a CIK or filing entity to structured-finance deals, funds, source documents, or facts JSON.https://data.sec.gov/api/xbrl/companyfacts/CIK0001018724.json
What should I use for agent retrieval?
Start with
,
,
, and entity facts files.
Pair DealCharts facts with SEC source URLs whenever your answer needs citation.