Offerings and capital raises

All Filings Search - Regulation A

POSThttps://api.sec-api.io/reg-a/search

Search the Part I notification data of every Form 1-A, 1-K and 1-Z filing published on SEC EDGAR since June 2015 with a Lucene expression. All three Regulation A form types sit behind this one endpoint, so a single query by cik or fileNo returns the whole lifecycle of an offering. New filings are searchable 300 milliseconds after EDGAR publishes them.

Read the guide for this API →

Authentication

Send the API key either as a header or as a query parameter. The header is preferred; the query parameter exists for cases where a header cannot be set, such as opening a URL directly in a browser.

Authorization: required header

The API key on its own. Do not prefix it with Bearer or any other word.

Example Authorization: YOUR_API_KEY

token: optional query parameter

The API key, appended to the URL. Use this only when a header is not possible.

Request body

A JSON object. Content-Type must be application/json.

query: required string

The search expression in Lucene syntax, written as field:value. Every field listed under Searchable fields can be used, combined with AND, OR, NOT, ranges and wildcards.

Example cik:1989528

from: integer, Maximum 10000

Index of the first result to return, used for pagination. Increment by the value of size to page through results.

Default 0

size: integer, Maximum 50

Number of filings to return in one response.

Default 50

sort: array of object

Sort order. Each item maps one field to an order object, for example [{ "filedAt": { "order": "desc" } }].

Default [{ "filedAt": { "order": "desc" } }]

order: string

Either asc or desc.

Searchable fields

Every field below can be used inside query. 186 fields are searchable, and they match the structure of the objects returned in the response.

FieldDescription
accessionNoUnique EDGAR accession number, e.g. "0001731122-24-001065"
fileNoEDGAR file number tying related filings together (e.g. "024-12457")
formTypeForm type — "1-A", "1-A/A", "1-A POS", "1-A-W", "1-K", "1-K/A", "1-Z", "1-Z/A"
filedAtDate the filing was accepted by EDGAR
periodOfReportReporting period covered by the filing (fiscal year end on annual reports)
cikIssuer CIK (leading zeros removed)
tickerIssuer ticker symbol at time of filing (if any)
companyNameIssuer legal name

Response

A JSON object. Nested attributes are collapsed; expand one to see its fields.

total: object

How many filings matched the query.

value: integer

Number of matching filings, capped at 10000. A value of 10000 with relation gte means more than 10000 filings matched.

relation: string

Either eq, meaning value is exact, or gte, meaning value is a floor.

data: array of object

The matching filings, at most size per response. Which blocks a filing object carries depends on its form type, so each form-specific attribute below names the form it belongs to. Form 1-A-W filings hold no structured data on EDGAR, so only id through companyName are returned for them.

id: string

System-internal unique identifier of the filing record.

accessionNo: string

Unique accession number of the filing, for example 0001731122-24-001065.

fileNo: string

EDGAR file number tying the filings of one offering process together, for example 24R-00889. Searching by fileNo returns the full lifecycle of a single offering.

formType: string

Form type of the filing. Values: 1-A, 1-A/A, 1-A POS, 1-A-W, 1-K, 1-K/A, 1-Z, 1-Z/A.

filedAt: string

Timestamp EDGAR accepted the filing, ISO 8601 in Eastern Time, for example 2024-05-15T16:17:15-04:00.

periodOfReport: optional string

Reporting period covered by the filing, YYYY-MM-DD. On annual reports this is the fiscal year end.

cik: string

CIK of the reporting entity, leading zeros removed.

ticker: string

Ticker symbol of the filer at the time of filing, where the filer is publicly traded. Empty string otherwise.

companyName: string

Legal name of the issuer as given in the filing.

Status codes

200Success. The response holds total and data.
400The request body could not be parsed, or the Lucene expression in query is malformed.
403The API key is missing, or it is not valid.
429Too many requests. Slow the request rate and retry.
500Server error. Retry, and report it if it persists.