Filing Download & PDF Generator API

Use the Download API at https://archive.sec-api.io to retrieve the original HTML of a 10-K. Take the filing's primary document URL on EDGAR (the linkToFilingDetails value, for example a URL ending in aapl-20230930.htm), keep everything after /data/, and request that path against the Download API. The endpoint returns the file content unchanged, so a request for an .htm document comes back as text/html exactly as it was published.

The Download API does not transform the document; it serves the same bytes that EDGAR hosts. If you instead want a print-ready version of the same annual report, the PDF Generator API at https://api.sec-api.io/filing-reader converts that HTML document to PDF.

Take the original EDGAR file URL (the linkToFilingDetails, linkToTxt, or any document URL inside documentFormatFiles) and replace the https://www.sec.gov/Archives/edgar/data prefix with the Download API host https://archive.sec-api.io. In other words, append the path that follows /data/ to https://archive.sec-api.io. For example, the EDGAR URL https://www.sec.gov/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm becomes https://archive.sec-api.io/815094/000156459021006205/abmd-8k_20210211.htm.

The path that follows /data/ always consists of the filer CIK, the accession number without hyphens, and the file name. The original EDGAR file path can always be used directly with the Download API in this way.

The Download API at https://archive.sec-api.io accepts the three identifiers directly in the path, in the form https://archive.sec-api.io/<cik>/<accession-number>/<filename>. The <cik> is the filer's CIK without leading zeros (for example 815094, drawn from the cik field), the <accession-number> is the accession number with all hyphens removed (for example 000156459021006205 rather than 0001564590-21-006205, derived from the accessionNo field), and <filename> is the name of the document you want.

No other lookup step is needed: assembling those three values into the path is enough to retrieve the original file. The new beta endpoint https://edgar-mirror.sec-api.io accepts the same path structure if you want higher throughput.

Each filing has a complete submission text file that bundles every document, exhibit, and the SGML header into a single .txt file. Its URL is stored in the linkToTxt field (for example https://www.sec.gov/Archives/edgar/data/19617/000121390021012092/0001213900-21-012092.txt), and the same file also appears in documentFormatFiles as the entry whose description is Complete submission text file.

To download it, take that linkToTxt URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host. The endpoint returns the full submission text rather than an individual rendered document.

Individual exhibits are listed in the documentFormatFiles array, each with its own document URL (documentFormatFiles.documentUrl) and an exhibit type (documentFormatFiles.type) such as EX-99.1 for an exhibit attachment. A material contract is filed under Exhibit 10, an underwriting agreement under Exhibit 1, and a list of subsidiaries under Exhibit 21. To download one specific exhibit, take its documentUrl and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The Download API serves each exhibit as its own file, so you retrieve only the attachment you ask for rather than the whole submission. This is the approach for monitoring specific exhibits, for example tracking material contracts for compliance.

Use the PDF Generator API at https://api.sec-api.io/filing-reader to convert a Form 3, 4, or 5 insider trading report into a PDF. The endpoint takes the URL of the original filing document and returns the rendered file with a content type of application/pdf, preserving the original formatting including tables and images.

Insider reports are typically stored as XML, so use the document URL from linkToFilingDetails or the matching documentFormatFiles entry. If that URL points at the inline XBRL viewer (it contains /ix?doc=), remove /ix?doc= from the URL before passing it to the PDF Generator API. The resulting PDF is suitable for sharing, printing, and archiving.

The PDF Generator API endpoint https://api.sec-api.io/filing-reader produces a printable PDF of a 10-K. It is a GET-only endpoint and takes two required values: token, which is your API key, and url, which is the address of the original filing document on EDGAR (a valid sec.gov/Archives URL, such as the 10-K's linkToFilingDetails value).

The response content type is application/pdf, and the original layout, including tables and images, is preserved. Invisible inline XBRL tags are stripped out so the resulting PDF stays smaller. If the url you have contains the inline XBRL viewer segment /ix?doc=, remove that segment before using it.

XBRL and other structured data files are listed in the dataFiles array of a filing, and when a filing carries XBRL the linkToXbrl field holds the address of the XBRL document. To download an XBRL file, take that URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The Download API serves XBRL, XSD, and other data files in their original format without modification, so the file is ready for parsing into your own financial analysis. Note that not every filing has XBRL attached; in those cases linkToXbrl is empty and dataFiles is an empty array.

Yes. Embedded images appear in the documentFormatFiles array as separate entries whose type is GRAPHIC (for example a .jpg file like image_001.jpg attached to a prospectus). Each one has its own document URL in documentFormatFiles.documentUrl. To download an image, take that URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The Download API supports all MIME types and returns the image with the matching content type, such as image/png or the original JPEG, so the graphic comes back exactly as it was filed.

Authenticate to the Download API at https://archive.sec-api.io by setting your API key as the value of the Authorization header. The key is used directly as the header value with no prefix; do not add the word Bearer or any other text in front of it.

This header-based method keeps the API key out of the URL, which is useful when you do not want the key recorded in logs or browser history. When you use the official Python or Node.js SDK, the key is added to the request headers for you automatically.

The Download API at https://archive.sec-api.io accepts the API key as the token query parameter appended to the request URL, for example https://archive.sec-api.io/path/to/edgar-file?token=YOUR_API_KEY. Whenever you would request a file path, you add ?token=YOUR_API_KEY to the end of that URL.

This is the alternative to passing the key in the Authorization header, and it is convenient when you want to open a download link directly in a browser. The PDF Generator API at https://api.sec-api.io/filing-reader also uses a token parameter for the same purpose.

When an EDGAR URL points at the inline XBRL viewer it contains the segment /ix?doc=, for example https://www.sec.gov/Archives/edgar/data/.../ix?doc=/Archives/edgar/data/.../doc.htm. Before passing such a URL to the PDF Generator API at https://api.sec-api.io/filing-reader, remove the /ix?doc= segment so the url value points directly at the underlying document.

After that cleanup the url is a plain sec.gov/Archives document address, which is the form the PDF Generator API requires. The endpoint then renders the document itself rather than the viewer wrapper.

New EDGAR files, including filings, exhibits, and attachments, become accessible through the Download API at https://archive.sec-api.io in approximately 300 milliseconds after they are published on EDGAR, and in all cases in less than 600 milliseconds.

This applies to any new document; once a filing is live on EDGAR you can request its path against the Download API almost immediately by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The Download API supports up to 60,000 downloads per API key within a five-minute window. The standard endpoint https://archive.sec-api.io is rated at 50 requests per second, while the original EDGAR file URLs are limited to 10 requests per second.

The new beta endpoint https://edgar-mirror.sec-api.io raises the per-second cap to 200 requests per second, still within the same 60,000-files-per-five-minute allowance. If you need throughput beyond a single client's pace, the beta endpoint has an overall capacity of more than one million requests per second.

The beta endpoint https://edgar-mirror.sec-api.io is the higher-throughput option for bulk downloads. It is a drop-in replacement for the standard Download API at https://archive.sec-api.io: you simply swap the host and keep the same <cik>/<accession-number>/<filename> path structure.

The difference is in capacity and rate limits. The standard endpoint is rated at 50 requests per second, while the beta endpoint allows up to 200 requests per second and has an overall capacity of more than one million requests per second. The beta endpoint also accepts more path variants, including CIKs with leading zeros and the full Archives/edgar/data/... path. During the beta, bandwidth is free for early adopters.

The beta endpoint https://edgar-mirror.sec-api.io works as a direct replacement for the SEC host. Take any original EDGAR file URL and replace https://www.sec.gov with https://edgar-mirror.sec-api.io, leaving the rest of the path unchanged. For example, https://www.sec.gov/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm becomes https://edgar-mirror.sec-api.io/Archives/edgar/data/815094/000156459021006205/abmd-8k_20210211.htm.

This returns the same content as the SEC site but with higher rate limits. The beta endpoint also accepts the shorter <cik>/<accession-number>/<filename> path form if you prefer not to keep the full Archives/edgar/data prefix.

Yes. The Download API at https://archive.sec-api.io is survivorship-bias free: it serves filings, exhibits, and attachments from all 800,000-plus EDGAR filers, including companies that have ceased to file as well as those still active.

As long as you have the filer CIK, accession number, and file name (the cik and accessionNo values plus a document URL from documentFormatFiles), you can request the file regardless of whether the company is still in operation. Filings of acquired, delisted, or dissolved entities remain available.

The Download API at https://archive.sec-api.io covers all EDGAR filings from 1993 and 1994 through the present, spanning more than 20 million filings and more than 100 million exhibits and attachments across all 400-plus EDGAR form types.

Historical documents are served the same way as recent ones: take the original EDGAR URL and replace the https://www.sec.gov/Archives/edgar/data prefix with the Download API host. Older legacy filings from the 1990s are available, though they were filed as plain text rather than HTML.

For large-scale 10-K downloads, use the beta endpoint https://edgar-mirror.sec-api.io, which is the higher-throughput option, rated at up to 200 requests per second within an allowance of 60,000 files per five-minute window. Each request follows the path form https://edgar-mirror.sec-api.io/<cik>/<accession-number>/<filename>, where the values come from each filing's cik, accessionNo (hyphens removed), and a document URL in documentFormatFiles.

The Download API itself only retrieves files; you first need the list of 10-K document URLs to fetch. Those are obtained from the filing metadata returned by the pull-based filing Query API at /full-text-search or the real-time Stream API, which provide the linkToFilingDetails and documentFormatFiles entries. You then iterate over those URLs against the beta endpoint. For training a language model on filing text, request the original HTML or text document rather than the PDF version.

Legacy filings from the early years of EDGAR were submitted as plain .txt documents rather than HTML. The text document is reachable through the linkToTxt field or the corresponding .txt entry in documentFormatFiles. To download it, take that URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The endpoint returns the file with a text/plain content type, unchanged from how it was filed. For text analysis, NLP, or RAG tasks on these older filings, the raw text content is preferred over a converted PDF.

The documentFormatFiles array lists every document in a submission, and each entry carries a documentFormatFiles.sequence number and a documentFormatFiles.type. The primary filing is the entry with sequence 1 whose type matches the form type itself (for example type 8-K for an 8-K, or SC14D9C for that form), and its URL also matches the filing's linkToFilingDetails. Supporting exhibits carry types such as EX-99.1 or GRAPHIC, and the bundled submission file is the entry whose description is Complete submission text file.

Once you have identified the entry you want, take its documentFormatFiles.documentUrl and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

Use the PDF Generator API at https://api.sec-api.io/filing-reader to render a proxy statement (Form DEF 14A) as a PDF. The endpoint converts the HTML document while preserving the original formatting, including tables and images, and it optimizes and scales embedded images for high-quality printing such as the graphics common in proxy statements.

Provide the proxy statement's document URL from linkToFilingDetails as the url value and your API key as token. The response comes back with a content type of application/pdf. Invisible inline XBRL tags are removed during conversion so the resulting PDF stays compact.

Legacy text-based .txt filings were never designed for printable page output. When the PDF Generator API at https://api.sec-api.io/filing-reader converts one, a single table row can span multiple lines and may not fit within the standard A4 page width, so the result can look misaligned.

For NLP, LLM, or RAG-based tasks on these older filings, use the original text content instead of the PDF version. Retrieve that text by taking the filing's linkToTxt URL and requesting it through the Download API at https://archive.sec-api.io, which gives better accuracy for parsing.

The Download API at https://archive.sec-api.io returns each file with a MIME content type that matches the requested file. An HTML document comes back as text/html, an XML document as text/xml, an image as a type such as image/png, and so on across HTML, XML, XSD, XBRL, TXT, PDF, Excel, Word, ZIP, and image files.

By default the response body is compressed with gzip. Most clients, such as browsers and standard Python or Node.js HTTP libraries, decompress the response automatically. If you use a low-level HTTP client, your application has to handle the gzip decompression itself.

Form 4 insider trading reports are filed as XML documents. The XML file is listed in documentFormatFiles with a type of 4, and its address is also the filing's linkToFilingDetails value (for example a URL ending in doc1.xml or wf-form4_155088062561750.xml). To download it, take that URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The endpoint returns the XML with a text/xml content type, unchanged. Note that EDGAR also publishes a styled version of the same document under an xslF345X03/ path; request the plain XML URL if you want the raw machine-readable form. To get the Form 4 as a PDF instead, pass that XML URL to the PDF Generator API at https://api.sec-api.io/filing-reader.

SEC-generated correspondence appears in EDGAR as an UPLOAD submission with a description of Form UPLOAD - SEC-generated letter and a formType of LETTER. Its document is reachable through linkToFilingDetails (for these letters often a .pdf such as filename1.pdf) and is also listed in documentFormatFiles with a type of LETTER. To download it, take that document URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The Download API serves these letters in their original format, so a .pdf letter comes back as application/pdf. The accompanying text extract, when present, is another documentFormatFiles entry with a type such as TEXT-EXTRACT.

When a filing is submitted jointly, the entities array lists every related filer, each with its own CIK and file number, but the submission has a single set of documents in documentFormatFiles. There is one shared accession number (accessionNo) and one primary document at linkToFilingDetails. To download that shared document, take its URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

You do not need a separate request per entity; the document URL is the same for all of them. The CIK embedded in the document path is the filing agent's path CIK, and the same file serves the whole group of joint filers.

Yes. The Download API at https://archive.sec-api.io can fetch original EDGAR filings on demand so they can be displayed on an investor relations website. Take the document URL from a filing's linkToFilingDetails or documentFormatFiles, replace the https://www.sec.gov/Archives/edgar/data prefix with the Download API host, and serve the returned content, which preserves the original HTML, XML, or text.

If you want to present filings as PDFs instead, the PDF Generator API at https://api.sec-api.io/filing-reader converts the same documents to application/pdf. Displaying EDGAR filings in different formats on investor relations sites is one of the listed use cases for these endpoints.

Prospectus and pricing supplement documents are filed under form types in the 424B family (such as 424B2, 424B3, 424B4, 424B5) tied to a registration statement. The primary document is at linkToFilingDetails and is listed in documentFormatFiles with a type matching the form, for example 424B2 with a description of PRICING SUPPLEMENT. To download it, take that URL and request it through the Download API at https://archive.sec-api.io by replacing the https://www.sec.gov/Archives/edgar/data prefix with the Download API host.

The endpoint returns the document in its original format. To produce a PDF of the prospectus instead, pass that document URL to the PDF Generator API at https://api.sec-api.io/filing-reader, which keeps tables and images intact.

Both endpoints are GET only. The Download API at https://archive.sec-api.io (and its beta replacement https://edgar-mirror.sec-api.io) supports the GET HTTP method, and the PDF Generator API at https://api.sec-api.io/filing-reader also supports only GET.

POST requests are not supported by either endpoint. Each request is fully expressed in the URL: a file path for the Download API, and the token and url query parameters for the PDF Generator API.