# EDGAR File & SEC Filings Download API > Download all 20 million SEC EDGAR filings and 100 million exhibits and attachments from 1993 to the present, at up to 200 requests per second. Original HTML, TXT, XML, XBRL, Excel, PDF and image files, preserved as filed. Source: https://sec-api.io/docs/edgar-file-and-sec-filings-download-api The Filing Download API supports downloading all 20 million SEC filings, and all 100 million exhibits, attachments, and other EDGAR files from any of the 800,000 filers between 1993/1994 to the present. All EDGAR form types are accessible and the API supports up to 60,000 downloads per API key within a five-minute window. The Download API has a total throughput capacity of over 1 million requests per second, and provides access to more than 1,000 terabytes of SEC filings data, including original filing publications in HTML/TXT format, filing index pages, SGML headers, complete submission files, PDFs, images, XML and XBRL files, Excel files, and many more. New EDGAR files (filings, exhibits, etc.) are accessible via the Download API in approximately 300 milliseconds after publication on EDGAR. Mapping of EDGAR Filing URL to Download API and New Endpoint ``` ┌──────────────────────────────────────────────────────────────────────────────┐ │ Original EDGAR File URL │ │ 10 requests / second │ └──────────────────────────────────────────────────────────────────────────────┘ https://www.sec.gov/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm │ │ ▼ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Download API URL │ │ 50 requests / second │ └──────────────────────────────────────────────────────────────────────────────┘ https://archive.sec-api.io/815094/000156459021006205/abmd-8k_20210211.htm │ │ ▼ ┌──────────────────────────────────────────────────────────────────────────────┐ │ New Download API URL (Beta) │ │ Capacity of 1+ million requests / second │ └──────────────────────────────────────────────────────────────────────────────┘ https://edgar-mirror.sec-api.io/815094/000156459021006205/abmd-8k_20210211.htm https://edgar-mirror.sec-api.io/0000815094/000156459021006205/abmd-8k_20210211.htm https://edgar-mirror.sec-api.io/000156459021006205/abmd-8k_20210211.htm https://edgar-mirror.sec-api.io/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm ``` All 400+ EDGAR form types are accessible, including annual and quarterly reports (Forms 10-K, 10-Q, 20-F, 40-F), event-driven disclosures (Forms 8-K, 6-K), registration statements (S-1, S-3, S-4, S-8, F-1, etc.), prospectuses (424B2, 424B4, 424B5, etc.) insider trading reports (Forms 3, 4, 5), proxy statements (DEF 14A), voting records (PRE 14A, N-PX), and any other type. Examples of available exhibits are Exhibit 1 (Underwriting Agreement), Exhibit 8 (Opinion Re Tax Matters), Exhibit 16 (Letter Re Change in Certifying Accountant), Exhibit 21 (Subsidiaries), [and all other existing exhibits](https://sec-api.io/list-of-sec-filing-types#edgar-filing-exhibits). All original file formats and contents are preserved and provided as-is without modifications. Content types include HTML, XML, XSD, XBRL, TXT, PDF, Excel, Word, ZIP, and image files. To convert an HTML, XML or TXT filing into a PDF, use the [PDF Generator API](https://sec-api.io/docs/sec-filings-to-pdf-generator-api) instead. Dataset size: All 20+ million SEC EDGAR filings, and all 100+ million exhibits, and attachments filed since 1993 to present. Includes HTML, TXT, XML, PDF, Excel files, images, and more. Covers all EDGAR form types, such as 10-K, 10-Q, 8-K, S-1, DEF 14A. Data update frequency: New filings, exhibits, and attachments are available in less than 600 milliseconds after they are published on EDGAR. Survivorship bias free: Yes. All filings, exhibits, and attachments are available from all 800,000+ EDGAR filers, including those that are active and those that have ceased to file. ## Use Cases The Download API is often used alongside the [real-time filing Stream API](https://sec-api.io/docs/stream-api) or the [pull-based filing Query API](https://sec-api.io/docs/query-api). Filings or exhibit URLs pointing to the sec.gov source are typically retrieved from the metadata returned by the Stream or Query API, and these URLs are then used to download the content. Use cases include: - Download historical filings, such as annual reports on Form 10-K, to train LLMs or perform textual analysis - Display EDGAR filings in different formats on investor relationship websites - Access and monitor specific filing exhibits, such as material contracts, for compliance - Download original XBRL files for financial analysis ## Download API Filings, exhibits and attachments can be downloaded by calling the Download API endpoint with the path to the original file on SEC EDGAR. The Download API returns the original file content, such as HTML, XML or TXT. ### API Endpoint https://archive.sec-api.io Supported HTTP Request Method: `GET` New Endpoint (Beta) https://edgar-mirror.sec-api.io Rate limit:Up to 200 requests/second (60,000 files per 5-minute interval) Bandwidth costs:Free during beta for early adopters. Users who join during beta will keep free bandwidth forever. This endpoint is a drop-in replacement for: - the existing Download API. Replace `https://archive.sec-api.io` with `https://edgar-mirror.sec-api.io` to access all EDGAR filings, exhibits, and attachments with improved rate limits. - the original SEC EDGAR file URLs. Simply replace `https://www.sec.gov` with `https://edgar-mirror.sec-api.io` to access the same content with higher rate limits. The response content type depends on the requested file. For instance, requesting a HTML file returns a `text/html` MIME content type. The API supports all MIME types, such as `text/xml` for XML files or `images/png` for images. By default, transmitted content between the Download API and a client application is compressed with gzip. Typically, the response is automatically decompressed by the client application, such as a browser or a Python/Node.js script. In case of low-level HTTP requests, the decompression needs to be handled by the client application. ### Authentication Two authentication methods are available. Choose the method that best fits your use case: - **Authorization header**: Set the API key as the value of the `Authorization` header. Do not add "Bearer" or any other words in front of the API key. Example: `Authorization: YOUR_API_KEY` - **Query parameter**: Set the API key as the `token` query parameter. Example: `https://archive.sec-api.io/path/to/edgar-file?token=YOUR_API_KEY`. Instead of performing requests to `https://archive.sec-api.io/path/to/edgar-file`, you always append `?token=YOUR_API_KEY` to the end of the URL. When using the Python or Node.js SDK, the API key is automatically added to the request headers. ### Request Parameters The Download API accepts the file path of the original SEC EDGAR URL. A generic example looks like this: https://archive.sec-api.io/// New Endpoint (Beta) https://edgar-mirror.sec-api.io/// - ``: The filer's CIK, without leading zeros, e.g. 815094. - ``: The filing's accession number, using only numeric characters (hyphens removed). For example, 000156459021006205 instead of 0001564590-21-006205. - ``: The name of the file (any file type is supported). All three values can be obtained from the original file URL and the original file path on SEC EDGAR can always be used directly with the Download API. Mapping of original EDGAR URL to Download API and new beta endpoint ``` ┌───────────────────────────────────────────────────────────────────────────┐ │ Original EDGAR File URL │ └───────────────────────────────────────────────────────────────────────────┘ https://www.sec.gov/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm │ │ ▼ ┌───────────────────────────────────────────────────────────────────────────┐ │ Download API URL │ └───────────────────────────────────────────────────────────────────────────┘ https://archive.sec-api.io/815094/000156459021006205/abmd-8k_20210211.htm │ │ ▼ ┌───────────────────────────────────────────────────────────────────────────┐ │ New Endpoint (Beta) │ └───────────────────────────────────────────────────────────────────────────┘ https://edgar-mirror.sec-api.io/815094/000156459021006205/abmd-8k_20210211.htm https://edgar-mirror.sec-api.io/0000815094/000156459021006205/abmd-8k_20210211.htm https://edgar-mirror.sec-api.io/000156459021006205/abmd-8k_20210211.htm https://edgar-mirror.sec-api.io/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm ``` ### Examples For example, to download the filing with the URL: https://www.sec.gov/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm The path after `data/` is appended to the Download API endpoint like this: https://archive.sec-api.io/815094/000156459021006205/abmd-8k_20210211.htm Similarly, to download the same filing using the new beta endpoint, the URL would be: https://edgar-mirror.sec-api.io/815094/000156459021006205/abmd-8k_20210211.htm ```bash https://edgar-mirror.sec-api.io/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm?token=YOUR_API_KEY ```