Filing Query API

To retrieve the latest quarterly reports, use the Query API endpoint (https://api.sec-api.io). The form type filter is the EDGAR code for quarterly reports, so the value of formType should be 10-Q. The endpoint returns filing metadata objects whose formType matches the query, with their accession number (accessionNo), filer identifiers (cik, ticker, companyName), and the EDGAR acceptance timestamp (filedAt).

The default sort already orders results by filedAt in descending order (newest first), so no custom sort is needed unless you want to override it. Set size up to the maximum of 50 per response, and step through pages by increasing from in increments of 50.

To pull all filings disclosed by a specific company, search the Query API endpoint (https://api.sec-api.io) for filings whose ticker matches the symbol of interest, for example AAPL for Apple. Ticker matching is case-insensitive, so AAPL and aapl return the same results. Each result includes the filer's identifiers (cik, ticker, companyName) and the EDGAR metadata (accessionNo, formType, filedAt, linkToFilingDetails).

For long historical searches, ticker-based queries can miss filings made when the company traded under a different symbol or filed under a separate share-class ticker. In those cases, resolve the ticker to a CIK first using the /mapping endpoint and then query on cik instead. If the universe contains more than 10,000 filings, split the query by a filedAt date range and paginate within each window using from in steps of size.

To pull every filing for a company by its CIK, query the Query API endpoint (https://api.sec-api.io) with the value of cik set to the issuer's CIK with the leading zeros removed — for example, Apple's CIK 0000320193 should be supplied as 320193. The response returns each filing's accessionNo, formType, filedAt, linkToFilingDetails, and the full entities array describing every party referenced on the filing.

CIK-based searches are the recommended approach for historical work because they survive ticker changes and cover all share classes the company has ever filed under. Use size up to 50 per response and increment from to paginate; if more than 10,000 filings match, split the query by filedAt date ranges.

To fetch filings for several companies at once, query the Query API endpoint (https://api.sec-api.io) with the value of ticker set to a parenthesized list of the symbols of interest, for example AAPL, MSFT, NVDA, and TSLA grouped together. The endpoint returns all matching filings interleaved, each carrying its own ticker, cik, companyName, formType, and filedAt.

The same parenthesized-list shape works for cik, which is the safer choice when any of the basket companies has changed ticker over the historical window you are searching. Pagination follows the standard pattern of size up to 50 and from incremented by size.

To retrieve a specific filing's metadata, query the Query API endpoint (https://api.sec-api.io) with the value of accessionNo set to the EDGAR accession number of the filing, for example 0001193125-23-265616. The response will return the matching filing object with its formType, filedAt, periodOfReport, linkToFilingDetails, documentFormatFiles, dataFiles, and the full entities array.

Note that the endpoint may return more than one filing object for a single accession number: for filings such as Form 4 that reference multiple parties (issuer and reporting person), the API creates a separate result per entity, each with its own internal id but the same accessionNo.

To list filings within a date window, query the Query API endpoint (https://api.sec-api.io) and constrain filedAt to the desired window — for instance, restrict filedAt to dates between 2022-01-01 and 2022-12-31 to retrieve every filing accepted by EDGAR during calendar year 2022. The bounds use the YYYY-MM-DD format and are inclusive on both ends.

If the window matches more than 10,000 filings, split it into smaller sub-windows (for example month by month) and paginate within each sub-window using from in steps of size. Each result carries the precise acceptance timestamp on filedAt, which is reported in Eastern Time.

To target a specific hour of the day, query the Query API endpoint (https://api.sec-api.io) and constrain filedAt with timestamps in the YYYY-MM-DDTHH:MM:SS format — for example, set the lower bound to 2021-09-15T14:00:00 and the upper bound to 2021-09-15T15:00:00 to retrieve filings accepted between 2:00 PM and 3:00 PM on September 15, 2021. Both bounds are inclusive.

You do not need to include a timezone offset: the API automatically interprets the timestamps in Eastern Time (the EDGAR system's reference timezone). The filedAt value returned on each filing carries the explicit offset (for example 2021-09-15T14:30:00-04:00) reflecting daylight savings as applicable.

To filter by industry, query the Query API endpoint (https://api.sec-api.io) and constrain the nested SIC code on the entities array — the value of entities.sic should be the four-digit SIC code of the industry, for example 3714 for motor vehicle parts and accessories or 6022 for state commercial banks. The SIC code is reported on the filer entity inside each filing's entities array.

Combine the industry filter with a formType constraint to narrow the scope further — for example, restrict to annual reports so that formType is 10-K. Each result's entities[0].sic field carries the matched SIC code and its plain-text description.

To restrict by state of incorporation, query the Query API endpoint (https://api.sec-api.io) and constrain the nested state field on the entities array — the value of entities.stateOfIncorporation should be the two-letter state code, for example DE for Delaware or NJ for New Jersey. The state is recorded on each entity inside the filing's entities array.

This filter matches the state on any entity referenced by the filing, which for most form types is the filer or issuer. Combine it with formType or filedAt to narrow the result set further.

To locate quarterly earnings announcements, query the Query API endpoint (https://api.sec-api.io) for current-event reports — the value of formType should be 8-K — and constrain the item codes so that items contains 2.02, the EDGAR item number for Results of Operations and Financial Condition. The endpoint returns Form 8-K filings whose items array includes a string starting with Item 2.02, along with the filer's ticker, cik, companyName, and the link to the filing detail page (linkToFilingDetails).

The earnings release itself is usually attached as Exhibit 99.1; you can spot it in the documentFormatFiles array by looking for an entry whose type is EX-99.1. To fetch the underlying document, pass the documentUrl to the /filing-reader endpoint of the Filing Download API.

To list Regulation FD disclosures, query the Query API endpoint (https://api.sec-api.io) for current-event reports — the value of formType should be 8-K — and constrain the item codes so that items contains 7.01, the EDGAR item number for Regulation FD Disclosure. The endpoint returns Form 8-K filings whose items array includes a string starting with Item 7.01.

The disclosed material is typically attached under Exhibit 99.1 inside the filing's documentFormatFiles array (documentFormatFiles.type set to EX-99.1). Combine the item filter with a filedAt date range or a specific ticker or cik to scope the search.

To find Form 8-K filings that touch on more than one event category, query the Query API endpoint (https://api.sec-api.io) for current-event reports — the value of formType should be 8-K — and constrain the item codes so that items matches any of the EDGAR item numbers of interest, for example 1.01 (Entry into a Material Definitive Agreement) together with 5.02 (Departure or Election of Directors and Certain Officers). The endpoint returns 8-K filings whose items array contains any of the requested item strings.

If you need filings that report all of the listed items rather than any of them, repeat the item constraint for each code so that every required item must be present, rather than only one. Each result's items array shows every event reported on that filing, so you can confirm which categories actually matched.

To pull annual reports that include the list of subsidiaries, query the Query API endpoint (https://api.sec-api.io) for annual reports — the value of formType should be 10-K — and constrain the nested exhibit type so that documentFormatFiles.type is EX-21, the EDGAR exhibit code for the subsidiary list. The endpoint returns the 10-K filings whose documentFormatFiles array contains an item of type EX-21.

Each matching filing's documentFormatFiles carries an entry with documentUrl pointing at the exhibit document on sec.gov. Pass that URL to the /filing-reader endpoint of the Filing Download API to retrieve the subsidiary listing itself.

To restrict to annual reports that include XBRL financials, query the Query API endpoint (https://api.sec-api.io) for annual reports — the value of formType should be 10-K — and constrain the nested data-file type on dataFiles.type to match the XBRL taxonomy file types, which all start with EX-101. (for example EX-101.INS for the instance document, EX-101.SCH for the schema, and EX-101.LAB for the label linkbase). The endpoint returns 10-K filings whose dataFiles array contains at least one entry of those types.

Each matching filing exposes the XBRL files in the dataFiles array, with the file URL on dataFiles.documentUrl and the precise taxonomy role on dataFiles.type. The instance document (EX-101.INS) is the canonical machine-readable record of the financial statements.

To locate annual reports that include images, query the Query API endpoint (https://api.sec-api.io) for annual reports — the value of formType should be 10-K — and constrain the nested exhibit type so that documentFormatFiles.type is GRAPHIC, the EDGAR type code assigned to image attachments such as JPGs and GIFs. The endpoint returns 10-K filings whose documentFormatFiles array contains at least one entry of type GRAPHIC.

Each graphic entry's URL is available on documentFormatFiles.documentUrl, and its size on documentFormatFiles.size. Filings can include many graphics — charts, logos, photos — and a single match is enough for the filing to surface in the results.

To search by exhibit type across all form types, query the Query API endpoint (https://api.sec-api.io) without a formType filter and constrain documentFormatFiles.type to the exhibit code of interest — for example EX-23.1 or EX-23.2 for auditor consent letters (the EX-23 family). Wildcards are supported, so a pattern that begins with EX-23 and ends with * matches every Exhibit 23 variant. The endpoint returns filings whose documentFormatFiles array contains a matching entry, regardless of the parent formType.

Each matched filing's documentFormatFiles shows the exhibit's documentUrl, description, and size. To fetch the exhibit document itself, pass the URL to the /filing-reader endpoint of the Filing Download API.

To filter by a specific share class or contract, query the Query API endpoint (https://api.sec-api.io) and constrain the nested class/contract identifier so that seriesAndClassesContractsInformation.classesContracts.classContract matches the class/contract ID of interest, for example C000120702. The endpoint returns filings whose seriesAndClassesContractsInformation array contains a classesContracts entry whose classContract matches.

The matched object also carries the human-readable class name on seriesAndClassesContractsInformation.classesContracts.name and, when available, the ticker on seriesAndClassesContractsInformation.classesContracts.ticker. Combine the class/contract filter with formType to narrow to a specific fund form, such as Form N-PORT.

To search by a fund share class ticker, query the Query API endpoint (https://api.sec-api.io) and constrain the nested class/contract ticker so that seriesAndClassesContractsInformation.classesContracts.ticker matches the symbol of interest, for example ABRZX. The endpoint returns filings whose seriesAndClassesContractsInformation array contains a classesContracts entry whose ticker matches the supplied symbol.

Using the class-ticker path is the right approach when you want to scope results to a single share class rather than every class of the parent fund (the top-level ticker field is not populated for many mutual fund filers). Each match carries the parent series identifier on seriesAndClassesContractsInformation.series and the class name on seriesAndClassesContractsInformation.classesContracts.name.

To list N-PORT filings for a specific share class, query the Query API endpoint (https://api.sec-api.io) and combine two constraints: the form type filter so that formType is NPORT-P, and the nested class/contract identifier so that seriesAndClassesContractsInformation.classesContracts.classContract matches the class/contract ID of interest, for example C000120702. The endpoint returns the public N-PORT filings whose class/contract list includes the requested identifier.

The periodOfReport field on each Form N-PORT filing represents the quarter-end date the report covers, which is useful when you want to sort the results chronologically by reporting period rather than by filedAt.

To search by IRS Employer Identification Number, query the Query API endpoint (https://api.sec-api.io) and constrain the nested IRS number on the entities array so that entities.irsNo matches the EIN of interest, for example 710388071. The endpoint returns filings whose entities array contains an entry whose irsNo matches.

The EIN is recorded on the filer/issuer entity inside entities and is a stable identifier for the legal entity, which is helpful when ticker or company name searches do not disambiguate. Each result's matching entity also carries companyName, cik, and stateOfIncorporation.

To search by SEC file number, query the Query API endpoint (https://api.sec-api.io) and constrain the nested file number on the entities array so that entities.fileNo matches the file number of interest, for example 001-36743. The endpoint returns filings whose entities array contains an entry whose fileNo matches the supplied value.

File numbers are issued by the SEC at registration and identify the registrant under a specific act (for example 001- prefixed numbers for Exchange Act registrations). The matched entity inside entities also carries the registrant's companyName, cik, and act.

To exclude amendments, query the Query API endpoint (https://api.sec-api.io) and constrain formType so that it is 10-K but is not 10-K/A. EDGAR uses the /A suffix on the form type to mark an amendment, so excluding any value that ends in /A leaves only the originals. The same approach works for other forms with amendment variants, such as 8-K versus 8-K/A or 13F-HR versus 13F-HR/A.

Each returned filing's formType field carries the exact form code, so you can confirm the result set contains no /A variants. If you instead want only amendments, invert the constraint so that formType is the /A variant.

To pull a year of insider transaction reports for one issuer, query the Query API endpoint (https://api.sec-api.io) and combine three constraints: the form type filter so that formType is any of 3, 4, or 5 (the EDGAR codes for initial, change-of, and annual statements of beneficial ownership); the issuer match so that cik is the issuer's CIK with leading zeros stripped, for example 320193 for Apple; and a filedAt window covering the past twelve months. The endpoint returns the insider filings whose issuer entity matches the supplied CIK within the window.

For Form 4 and similar filings, each filing references both an issuer and one or more reporting persons. The Query API creates a separate metadata object per entity, all sharing the same accessionNo, so the entities array on each result identifies which company is the issuer and which party is the reporting insider. To pull the actual transaction-level detail (codes, share counts, prices), pass the accession number to the Insider Trading dataset; the Query API itself returns only filing-level metadata.

To pull prospectus supplements for a single issuer, query the Query API endpoint (https://api.sec-api.io) and combine a form type filter — the value of formType should be 424B2, the EDGAR code for prospectus supplements filed under Rule 424(b)(2) used by many structured-note shelf programs — with the issuer match so that cik equals the issuer's CIK with leading zeros stripped, for example 19617. The endpoint returns the matching 424B2 filings with accessionNo, filedAt, and linkToFilingDetails.

Add a filedAt window if you want to scope the search to a specific calendar window. Related 424 sub-types (424B3, 424B4, 424B5, etc.) cover other Rule 424 variants — supply the appropriate code on formType for those.

To list registration statements that became effective in a given year, query the Query API endpoint (https://api.sec-api.io) and combine three constraints: the form type filter so that formType is EFFECT (the notice EDGAR posts when a registration statement becomes effective); the underlying registration form so that registrationForm is the form of interest, for example S-3; and a filedAt window covering the year. The endpoint returns EFFECT notices whose registrationForm matches.

Each EFFECT result also carries effectivenessDate (the date the registration became effective) and, when reported, effectivenessTime. Use effectivenessDate rather than filedAt if you want the calendar of effectiveness rather than the calendar of notice acceptance.

To trace an EFFECT notice back to the original registration statement, look at the referenceAccessionNo field on the EFFECT filing — it carries the accession number of the underlying registration that the notice made effective. Take that value and query the Query API endpoint (https://api.sec-api.io) with accessionNo set to the referenced accession number to retrieve the full metadata of the original registration filing.

The original filing's formType will match the registrationForm reported on the EFFECT notice (for example S-3, S-1, or F-3), and linkToFilingDetails gives the URL of the underlying registration document on sec.gov.

To see how many filings match a query before paginating, inspect the total object on the Query API response from the endpoint (https://api.sec-api.io). The numeric count is at total.value and the comparison qualifier is at total.relation. When total.relation is eq, the total.value is the exact match count. When total.relation is gte and total.value is 10000, the true count exceeds 10,000 and the API cannot enumerate beyond that cap.

If the relation is gte at the cap, the pagination strategy needs to slice the query into narrower sub-queries — typically by filedAt windows — and paginate each slice separately. If the value is below 10,000, a single sequence of from increments of size will retrieve the entire set.

The Query API endpoint (https://api.sec-api.io) caps each query at 10,000 matches (from cannot exceed 10,000 and total.value is capped at 10,000). To exhaust a broader universe, split the query along filedAt date ranges into windows that each fall below the cap — for a decade of Form 8-K traffic, narrow windows down to a month at a time (or shorter for high-volume months) so that each window's total.value is comfortably under 10,000.

For each window, page through the results by incrementing from in steps of size (maximum 50) until no more filings come back, then advance to the next window and repeat. Sort by filedAt in ascending or descending order consistently across all windows to keep the global ordering predictable.

To paginate as efficiently as possible against the Query API endpoint (https://api.sec-api.io), set size to its maximum of 50 and step from by 50 on each subsequent call — for example 0, 50, 100, and so on — until the response returns fewer than 50 filings or from reaches the hard cap of 10000. The default sort orders results by filedAt in descending order (newest first), which is stable as long as no new filings land mid-pagination at the front of the list.

If the query matches more than 10,000 filings (visible on total.relation set to gte with total.value at 10000), pagination alone cannot reach the rest — slice the query into narrower filedAt windows and paginate each window separately.

To sort by the reporting period instead of the EDGAR acceptance time, override the default sort against the Query API endpoint (https://api.sec-api.io) and order by periodOfReport in ascending or descending order. The periodOfReport field carries the period covered by the filing in YYYY-MM-DD format and has form-specific meaning — for example, fiscal year end for 10-K filings, transaction date for Form 4 filings, and quarter end for Form 13F filings.

Keep in mind that periodOfReport is only present on filings that report a period, so any matching filings without it will sort to the end. Combine the period sort with a filedAt window if you want a stable, bounded set across a paginated walk.