Query patterns

The questions the API gets asked most, each as a request you can copy. Every request on this page is executed against a live API instance by our regression suite before it ships — the curl line you paste is the one CI ran. Pass your key in the X-API-Key header (free keys take under a minute); the field-by-field contract behind every response is served machine-readable at GET /v1/schema.

Insider trades — Form 4

Every Form 4 arrives as one schema-v1 object: reporting owners, non-derivative and derivative transactions, holdings, footnotes — plus accession and filed_date merged in by the API. List responses use the envelope {"data": […], "total": n, "limit": n, "offset": n}, newest filed first.

Every insider filing for one company, newest first

One parameter. ticker matches the issuer's trading symbol case-insensitively. Each element of data is a complete filing — no follow-up request needed to see the transactions.

curl "https://api.filingpulse.io/v1/insider-trades?ticker=PRTH" \
  -H "X-API-Key: fp_your_key"

By CIK, when the ticker can't be trusted

The ticker on a Form 4 is whatever the filer typed — funds and BDCs routinely file NONE or N/A, and we keep values as filed. The CIK is assigned by the SEC, not typed, so it always identifies the issuer. Leading zeros are optional: 1841514 and 0001841514 are the same company.

curl "https://api.filingpulse.io/v1/insider-trades?cik=1841514" \
  -H "X-API-Key: fp_your_key"

Amendments only — or originals only

A Form 4/A corrects a previously filed Form 4. form_type=4/A returns only amendments; form_type=4 excludes them. Amended filings carry amendment_date — the date of the original being corrected.

curl "https://api.filingpulse.io/v1/insider-trades?form_type=4/A" \
  -H "X-API-Key: fp_your_key"

One filing by its accession number

The accession number is the SEC's stable id for a filing — unique across all of EDGAR, and it never changes. Every Form 4 object carries its own accession, so any row from a list response can be re-fetched, cited, or joined against EDGAR itself.

curl "https://api.filingpulse.io/v1/insider-trades/0001653558-26-000110" \
  -H "X-API-Key: fp_your_key"

Incremental sync without re-downloading history

since= bounds the window to filings filed on or after a date (it filters on filed_date, which every object carries). Page by advancing offset by limit until offset ≥ total; across polls, dedupe on accession. The watcher recipe is this pattern as a running program.

curl "https://api.filingpulse.io/v1/insider-trades?since=2026-08-01&limit=100" \
  -H "X-API-Key: fp_your_key"

curl "https://api.filingpulse.io/v1/insider-trades?since=2026-08-01&limit=100&offset=100" \
  -H "X-API-Key: fp_your_key"

Corporate events — 8-K

8-K filings classified by the SEC's official item codes. One filing often reports several items; the object's items array lists every code and caption as filed.

Every filing that reports a leadership change

Item codes are the SEC's own classification: 2.02 results of operations, 1.01 material agreements, 5.02 officer and director changes, 5.07 shareholder votes. item= matches any filing that lists the code — including filings that report several items at once.

curl "https://api.filingpulse.io/v1/events?item=5.02" \
  -H "X-API-Key: fp_your_key"

A digest of one event type over a window

Combine item= with since= (inclusive) for “every filing of this kind since…”. The 8-K digest recipe groups exactly this query by filing day.

curl "https://api.filingpulse.io/v1/events?item=5.07&since=2026-07-01" \
  -H "X-API-Key: fp_your_key"

Everything one company reported

cik= scopes events to one filer — CIK 793952 is Harley-Davidson. Add since= to bound the window; leading zeros are optional here too.

curl "https://api.filingpulse.io/v1/events?cik=793952" \
  -H "X-API-Key: fp_your_key"

IPO registrations — S-1 / F-1

Registration lifecycle events threaded by SEC file number: registration statements, pre-effective amendments, effectiveness notices, and priced prospectuses. Tracked live since Aug 1, 2026 — no backfill.

New registration statements in a window

stage= groups form types by lifecycle step: registration (S-1, F-1), amendment (S-1/A, F-1/A), effectiveness (EFFECT), prospectus (424B1, 424B4). This is the “what was newly registered this week” query.

curl "https://api.filingpulse.io/v1/registrations?stage=registration&since=2026-07-28" \
  -H "X-API-Key: fp_your_key"

One offering, first filing to pricing

The SEC file number (333-…) is EDGAR's own join key: every stage of one offering shares it, so this one filter returns everything we have tracked for a deal — file 333-297472 is Churchill Capital Corp XIII. Caveat: an EFFECT notice does not state which form went effective, so effectiveness rows also cover registrations we don't track (S-3, S-8, …); the file number tells you whether one belongs to a tracked offering.

curl "https://api.filingpulse.io/v1/registrations?file_number=333-297472" \
  -H "X-API-Key: fp_your_key"

Across datasets

The three datasets share one join key. These patterns cross them.

One company across all three datasets

CIK is the only identifier all three endpoints share — tickers exist only on Form 4, file numbers only on registrations. The same cik= reads a company's insider filings, its reported events, and its registration activity. CIK 1906364 is BOXABL.

curl "https://api.filingpulse.io/v1/insider-trades?cik=1906364" \
  -H "X-API-Key: fp_your_key"

curl "https://api.filingpulse.io/v1/events?cik=1906364" \
  -H "X-API-Key: fp_your_key"

curl "https://api.filingpulse.io/v1/registrations?cik=1906364" \
  -H "X-API-Key: fp_your_key"