EYARC

Analytics mindset case studies EDGAR Explorer two Submissions API

Analytics mindset

EDGAR Explorer – Case two

Submissions Application Programming Interface (API)

Background

Digital reporting of financial and nonfinancial business information continues to evolve and increase in importance. eXtensible Business Reporting Language, XBRL, is an XML standard for tagging business and financial reports using digital dictionaries or taxonomies. XBRL provides:

Our previous case, Analytics_Mindset_case studies_Edgar_Explorer_InlineXBRL, focused on Inline XBRL (iXBRL), which is an extension of XBRL. iXBRL combines XBRL with human-readable HTML. In iXBRL, the XBRL tags are embedded directly within the HTML document, making the financial information more accessible to both machines and humans. The tagged data is presented alongside the narrative text in a single document. The iXBRL documents are designed to be more user-friendly and accessible, as they provide a familiar HTML format for humans to read, while still allowing automated extraction of data for analysis.

The SEC requires domestic and foreign companies using US GAAP and foreign private issuers using International Financial Reporting Standards (IFRS) to provide their financial statements in the iXBRL format. iXBRL is a standardized format for financial reporting and the SEC has been using it to improve the accessibility and usability of financial data.

The SEC provides submissions history and XBRL data from company (filer) financial statements (Forms 10-Q, 10-K, 8-K, 20-F, 40-F, 6-K and their variants) in the Electronic Data Gathering, Analysis, and Retrieval (EDGAR) system via a Representational State Transfer (REST or RESTful) application programming interface (API).1 Using these services, users can download data about a company’s filings.

The following information outlines some common features of these APIs:

Submissions API

This case uses the SEC’s EDGAR Submissions API, which requires the user to know company CIK numbers. CIK numbers are assigned by the SEC to each entity that submits filings to the SEC. The SEC’s EDGAR website maintains a database of company names and tickers to help users look up a company’s unique CIK ID and access its filings. That website can be found at:

Depending upon the company you choose, there can be several CIK codes returned. Make sure you are selecting the correct company by verifying additional information. For example, one way to confirm the company is correct is to check the company’s address in the identifying information in the header, after clicking on the company link.

Once you have the CIK for the company, use the following SEC site to access the EDGAR Submissions API. You’ll need to replace the 10 hashes in the link with the company’s unique CIK code, at: https://data.sec.gov/submissions/CIK##########.json. For example, using Tesla’s CIK “0001318605,” the submissions file for Tesla can be found at:

The submissions file will contain metadata about the entity (including the CIK, company name, geographical and industry data) and a large amount of data describing the various disclosures made by the entity. This case explores the types and frequencies of disclosures made by a specific public company. Some of the information provided includes:

The Form 8-K filing reports on current significant events. These files are further classified into various types of events using an item number. For example, Item 4.01 relates to changes in the entity’s auditor and Item 9.01 requires any financial statements or exhibits be listed for any acquired business, funds or shell company.

Required

Footnotes

  1. The SEC’s API documentation is available at: https://www.sec.gov/edgar/sec-api-documentation.

    ↩
  2. “Financial Statement and Notes Data Sets,” SEC website, https://www.sec.gov/dera/data/financial-statement-and-notes-data-set.html, accessed November 2023.

    ↩