XBRL to JSON Converter API

Parse and standardize any XBRL data and convert it to standardized JSON format in seconds without coding. Extract financial statements from annual and quarterly reports (10-K, 10-Q, 20-F, 40-F), offerings such as S-1 filings, and post-effective amendements for registration statements (POS AM), accounting policies and footnotes, risk-return summaries of mutual fund and ETF prospectuses (485BPOS) and general information from event filings (8-K). All XBRL-supported filing types can be converterd.

Example: XBRL Income Statement from 10-K Filing in JSON Format


          1
          {
        

          2
            "StatementsOfIncome": {
        

          3
              "RevenueFromContractWithCustomerExcludingAssessedTax": [
        

          4
                {
        

          5
                  "decimals": "-6",
        

          6
                  "unitRef": "U_USD",
        

          7
                  "period": {
        

          8
                    "startDate": "2023-07-01",
        

          9
                    "endDate": "2024-06-30"
        

          10
                  },
        

          11
                  "value": "245122000000"
        

          12
                },
        

          13
                {
        

          14
                  "decimals": "-6",
        

          15
                  "unitRef": "U_USD",
        

          16
                  "period": {
        

          17
                    "startDate": "2022-07-01",
        

          18
                    "endDate": "2023-06-30"
        

          19
                  },
        

          20
                  "value": "211915000000"
        

          21
                },
        

          22
                {
        

          23
                  "decimals": "-6",
        

          24
                  "unitRef": "U_USD",
        

          25
                  "period": {
        

          26
                    "startDate": "2023-07-01",
        

          27
                    "endDate": "2024-06-30"
        

          28
                  },
        

          29
                  "segment": {
        

          30
                    "dimension": "srt:ProductOrServiceAxis",
        

          31
                    "value": "us-gaap:ProductMember"
        

          32
                  },
        

          33
                  "value": "64773000000"
        

          34
                },
        

          35
                // ... more revenue entries
        

          36
              ],
        

          37
              "CostOfGoodsAndServicesSold": [ "..." ],
        

          38
              "GrossProfit": [ "..." ],
        

          39
              "ResearchAndDevelopmentExpense": [ "..." ],
        

          40
              "SellingGeneralAndAdministrativeExpense": [ "..." ],
        

          41
              "OperatingExpenses": [ "..." ],
        

          42
              "OperatingIncomeLoss": [ "..." ],
        

          43
              "NonoperatingIncomeExpense": [ "..." ],
        

          44
              "IncomeTaxExpenseBenefit": [ "..." ],
        

          45
              "NetIncomeLoss": [ "..." ],
        

          46
              "EarningsPerShareBasic": [ "..." ],
        

          47
              "EarningsPerShareDiluted": [ "..." ],
        

          48
              "WeightedAverageNumberOfSharesOutstandingBasic": [ "..." ],
        

          49
              "WeightedAverageNumberOfDilutedSharesOutstanding": [ "..." ]
        

          50
              // ... more income statement items depending on the company
        

          51
          }

The entire US GAAP taxonomy is fully supported. All XBRL items are fully converted into JSON, including us-gaap, dei and custom items. XBRL facts are automatically mapped to their respective context including period instants and date ranges.

Any XBRL can be directly converted into Python pandas dataframes.

All financial statements and all US GAAP elements are supported, for example:

Income statement (consolidated statement of operations)
Balance sheet (consolidated statement of balance sheets)
Cash flow statement (consolidated statement of cash flows)
And many more.

Examples of Income Statement Items

RevenueFromContractWithCustomerExcludingAssessedTax
CostOfGoodsAndServicesSold
GrossProfit
ResearchAndDevelopmentExpense
SellingGeneralAndAdministrativeExpense
OperatingExpenses
OperatingIncomeLoss
NetIncomeLoss
EarningsPerShareBasic

Examples of Balance Sheet Items

AccountsReceivableNetCurrent
AccountsPayableCurrent
LiabilitiesCurrent
LongTermDebtCurrent
AssetsNoncurrent
RetainedEarningsAccumulatedDeficit
CashAndCashEquivalentsAtCarryingValue
InventoryNet

You can find a full list of all US-GAAP items authored by the Financial Accounting Standards Board here: https://www.fasb.org/xbrl

All cover page items are supported, for example:

DocumentPeriodEndDate
EntityFileNumber
EntityRegistrantName
EntityIncorporationStateCountryCode
EntityTaxIdentificationNumber
Security12bTitle
TradingSymbol
SecurityExchangeName
EntityPublicFloat
CurrentFiscalYearEndDate

Dataset size:

All XBRL data of any XBRL-friendly filing from 2005 to present.

Data update frequency:

XBRL-JSON data of new filings is available in less than 300 milliseconds after the filing is published on EDGAR.

Survivorship bias free:

Yes. The XBRL to JSON Converter API includes all XBRL data of any XBRL-friendly filing from 2005 to present, from filer entities that are still active and those that are no longer active.

Supported XBRL Filing Types

The following is a list of all supported filing types categorized by filer type:

Operating Companies:

10-K, 10-K/A, 10-KT, 10-KT/A, 10-Q, 10-Q/A, 10-QT, 10-12B, 10-QT/A, 10-12B/A, 10-12G, 10-12G/A, 8-K, 8-K/A, 8-K12B, 8-K12B/A, 8-K12G3, 8-K12G3/A, 8-K15D5, 8-K15D5/A, 20-F, 20-F/A, 20FR12B, 20FR12B/A, 20FR12G, 20FR12G/A, 40-F, 40-F/A, 40FR12B, 40FR12B/A, 40FR12G, 40FR12G/A, 6-K, 6-K/A, SP 15D2, SP 15D2/A, S-1, S-1/A, S-1MEF, S-3, S-3/A, S-3ASR, S-3D, S-3DPOS, S-3MEF, S-4, S-4/A, S-4EF, S-4MEF, S-4 POS, S-11, S-11/A, S-11MEF, POS AM, POS EX, POSASR, F-1, F-1/A, F-1MEF, F-3, F-3/A, F-3ASR, F-3D, F-3DPOS, F-3MEF, F-4, F-4/A, F-4EF, F-4MEF, F-4 POS, F-10, F-10/A, F-10EF, F-10POS, DEF 14A, DEF 14C, DEFA14A, DEFA14C, DEFC14A, DEFC14C, DEFM14A, DEFM14C, DEFR14A, DEFR14C, PRE 14A, PRE 14C, PREC14A, PREC14C, PREM14A, PREM14C, PRER14A, PRER14C

Attachement type

EX-101.*

Investment Companies:

485BPOS, 487, 497, 485APOS, 485BXT, N-1A, N-1A/A, N-2, N-2/A, N-2ASR, N-2 POSASR, N-2MEF, POS EX, POS462B, POS462C, 486BXT, 486APOS, 486BPOS, 486BXT, POS 8C, POS AMI, 424A, 424B1, 424B2, 424B3, 424B4, 424B5, 424B7, 424B8, N-CSR, N-CSR/A, N-CSRS, N-CSRS/A, SC 13E3, SC 13E3/A, DEF 14A, DEF 14C, DEFA14A, DEFA14C, DEFC14A, DEFM14A, DEFM14C DEFR14A, DEFR14C, 8-K, 8-K/A, 8-K12B, 8-K12B/A, 8-K12G3, 8-K12G3/A, 8-K15D5, 8-K15D5/A, 10-K, 10-K/A, 10-KT, 10-KT/A, 10-Q, 10-Q/A, 10-QT, 10-QT/A, 497, N-3, N-3/A, N-4, N-4/A, N-6, N-6/A, 497J, DEFC14C

Attachement type

EX-101.*

Security-Based Swap Data Repositories:

SDR, SDR/A, SDR-A, SDR-W

Attachement type

EX-99.SDR K.*, EX-99.SDR L.*

API Endpoint

XML-XBRL data attached to an EDGAR filing can be converted to JSON format by sending a GET HTTP request with the XBRL file URL, the HTML filing URL, or the accession number of the filing to the following endpoint:

https://api.sec-api.io/xbrl-to-json

Supported HTTP method: GET

Response content type: JSON. The response includes all XBRL items in JSON format.

Authentication

To authenticate requests to the XBRL to JSON Converter API, use the API key shown in your user profile. Utilize the API key in one of two ways. Choose the method that best fits your implementation:

Set as Authorization header. Before making a GET request to https://api.sec-api.io/xbrl-to-json, set the Authorization header to YOUR_API_KEY.
Set as query parameter ?token=YOUR_API_KEY: Perform a GET request to https://api.sec-api.io/xbrl-to-json?token=YOUR_API_KEY&htm-url=....

Request Parameters

The XBRL-to-JSON Converter API accepts three diferent query parameters for converting XBRL data to JSON. Provide the URL of the filing, the URL of the XBRL file, or the accession number of the filing. Choose the method that best fits your implementation:

htm-url: Provide the URL of the filing ending with .htm or .html. Both URLs, to the filing itself and the index page, are accepted.
Example URLs:
https://www.sec.gov/Archives/edgar/data/1318605/000156459021004599/tsla-10k_20201231.htm
https://www.sec.gov/Archives/edgar/data/914243/000091424322000011/0000914243-22-000011-index.html
xbrl-url: Provide the URL of the XBRL file ending with .xml. The XBRL file URL can be found in the dataFiles array returned by the Query API. The array item always has the description EXTRACTED XBRL INSTANCE DOCUMENT.
Example URLs:
https://www.sec.gov/Archives/edgar/data/1318605/000156459021004599/tsla-10k_20201231_htm.xml
https://www.sec.gov/Archives/edgar/data/914243/000091424322000011/ck0000914243-20210930_htm.xml
accession-no: Provide the accession number of the filing, e.g. 0001564590-21-004599

Utilize the Query API to generate a list of the most recent 10-K filings that include XBRL files. The search query format is as follows and can be tested in the sandbox.

formType:"10-K" AND dataFiles.description:"XBRL INSTANCE DOCUMENT"

Request Examples

The following examples demonstrate how to convert XBRL data to JSON using the XBRL-to-JSON Converter API with the three different query parameters: htm-url, xbrl-url, and accession-no.