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

# Does the SEC EDGAR API have segment data?

> No: the SEC's EDGAR APIs return facts for the whole company. Where revenue by segment, product and region is in SEC data, and one call that returns it.

No. The SEC's EDGAR APIs at `data.sec.gov` return a company's filing history and the XBRL facts that apply to the whole company, so you get Microsoft's total revenue and not the revenue of its Intelligent Cloud segment. Revenue by segment, product or region is a dimensional fact: a revenue concept on an axis, with a member. In SEC data you find it in each filing's own XBRL and in the SEC's Financial Statement and Notes data sets, as raw facts that you sum and check yourself. With numi, one request returns each breakdown already checked against the revenue the filing reports:

```bash theme={null}
curl "https://api.numi.sh/v1/companies/MSFT/segments" \
  -H "X-API-Key: $NUMI_API_KEY"
```

One axis of the response, the product axis, with two of its ten rows:

```json theme={null}
{
  "axis": "product",
  "reconciliation": "reconciled",
  "coverage_ratio": 1,
  "revenue_total": 331839000000,
  "currency": "USD",
  "segments": [
    {
      "member": "msft:ServerProductsAndCloudServicesMember",
      "label": "Server Products and Cloud Services",
      "revenue": 129425000000,
      "revenue_share": 0.390023
    },
    {
      "member": "msft:MicrosoftThreeSixFiveCommercialProductsAndCloudServicesMember",
      "label": "Microsoft 365 Commercial Products and Cloud Services",
      "revenue": 101997000000,
      "revenue_share": 0.307369
    }
  ]
}
```

## What each EDGAR API returns

The SEC describes these APIs on its page [EDGAR Application Programming Interfaces](https://www.sec.gov/search-filings/edgar-application-programming-interfaces). They need no API key. `##########` is the company's CIK in 10 digits, with leading zeros.

| API | Address | Returns | Revenue by segment |
| - | - | - | - |
| submissions | `https://data.sec.gov/submissions/CIK##########.json` | The company's name, former names, tickers and exchanges, and its filing history | No: it lists filings and has no financial facts |
| companyconcept | `https://data.sec.gov/api/xbrl/companyconcept/CIK##########/us-gaap/AccountsPayableCurrent.json` | Every XBRL disclosure of one concept by one company, one array per unit | No |
| companyfacts | `https://data.sec.gov/api/xbrl/companyfacts/CIK##########.json` | Every concept of one company in one call | No |
| frames | `https://data.sec.gov/api/xbrl/frames/us-gaap/AccountsPayableCurrent/USD/CY2019Q1I.json` | For one concept and one calendar period, one fact for each company: the fact filed last whose period fits that calendar period most closely | No |

## Why segment revenue is not in them

The SEC's page says that the three XBRL APIs aggregate facts that "Use a non-custom taxonomy (e.g. us-gaap, ifrs-full, dei, or srt)" and "Apply to the entire filing entity". A segment's revenue applies to one part of the company: the filing tags it with an axis, such as `us-gaap:StatementBusinessSegmentsAxis`, and a member, such as `msft:IntelligentCloudMember`. So companyfacts has Microsoft's consolidated revenue for each period, and none of its segments, product lines or regions.

## Where segment revenue is in SEC data

* **The filing's own XBRL:** each filing with XBRL in the EDGAR archive has its facts with their dimensions. You read it one filing at a time.
* **The Financial Statement and Notes data sets:** the SEC publishes them as monthly ZIP files on its page [Financial Statement and Notes Data Sets](https://www.sec.gov/data-research/sec-markets-data/financial-statement-notes-data-sets). In their `dim` table, the `segments` field has the tag names of the axis and members of each fact, so segment revenue is there as raw facts.

Either way, you get every member of every axis as filed: subtotals, second breakdowns of the same revenue and reconciling items sit beside the segments, and no field says whether the rows add up to the total. You keep one axis at a time, remove the rows that repeat other rows and compare the sum with the reported revenue. [How to get revenue by segment from SEC XBRL filings](https://docs.numi.sh/guides/revenue-by-segment-from-xbrl.md) gives the method step by step.

## The SEC's limits on automated access

The SEC asks each user to send no more than 10 requests a second, and to declare a User-Agent header with a company name and a contact email, on its page [Accessing EDGAR Data](https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data). Its page on the APIs adds that `data.sec.gov` does not support CORS, so code in a browser cannot call the APIs.

## The same breakdown from numi

Microsoft's 10-K for the fiscal year ended June 30, 2026 reports revenue of \$331.8 billion on three axes: three business segments, ten product lines and two regions. Each axis adds up to 100 percent of that revenue. The request at the top of this page returns each axis as its own list, with its rows, the filing's revenue total, the ratio of the rows to it and the `reconciliation` status, so your code reads one field to know whether a breakdown adds up. The `filing` in the response has the accession number and a link to the filing on EDGAR, where numi has matched it, so you can check each row at the source.

Microsoft is one of the 10 sandbox companies, so the call at the top of this page works as written with a free key from [numi.sh/account](https://numi.sh/account), with no card. See [segments](https://docs.numi.sh/segments.md) for every field, and [plans](https://docs.numi.sh/plans.md) for Builder, which has every company.


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