SEC EDGAR Filing Monitor (Company Filings JSON) avatar

SEC EDGAR Filing Monitor (Company Filings JSON)

Pricing

from $2.00 / 1,000 filing delivereds

Go to Apify Store
SEC EDGAR Filing Monitor (Company Filings JSON)

SEC EDGAR Filing Monitor (Company Filings JSON)

Get structured SEC EDGAR filings as JSON: metadata, accession numbers, and document URLs. Automate tracking of 10-K, 10-Q, and 8-K filings by CIK or full-text search. No login required; reliable and rate-limit aware.

Pricing

from $2.00 / 1,000 filing delivereds

Rating

0.0

(0)

Developer

Steadfetch

Steadfetch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Features

Limited permissions

Share

Extract official SEC EDGAR filing metadata as structured JSON: accession number, form type, filing dates, and primary document URLs. Supports CIK-based issuer tracking and full-text search. Public data, schema-validated, pay-per-event.

Tested daily. Last verified: 2026-11-03

What it does

  • Reads SEC EDGAR's public JSON endpoints: submissions at https://data.sec.gov/submissions/CIK##########.json, full-text search at https://efts.sec.gov/LATEST/search-index, and the filing index only to resolve the primary document when a full-text hit lands on an exhibit.
  • Returns filings by issuer cik, by full-text query, or both; providing both restricts the search to that issuer. A run with neither returns the latest filings of the example issuer (Apple Inc., CIK 0000320193) instead of failing.
  • Filters by formTypes (default 10-K, 10-Q, 8-K) and by inclusive date window startDate / endDate.
  • Paginates newest first, stops at maxResults, deduplicates by accession number, and pushes only records that pass the published dataset schema.
  • Applies the SEC access contract (declared User-Agent with a contact mailbox, 10 requests per second cap, 429/403/5xx backoff) and publishes filing metadata and issuer organisations only; officer, signatory and contact fields are excluded and scrubbed before push (GDPR).

How to use

  1. Install the Apify CLI (npm add -g apify-cli) and log in.

  2. Run the Store test input:

    $apify call steadfetch/sec-edgar-monitor --input='{"cik":"0000320193","formTypes":["10-K"],"maxResults":1}'
  3. Read the default dataset as JSON, CSV or the Store's table view.

  4. For scheduled monitoring, enable monitorMode (the default) so filings already delivered to your Apify user are not pushed again; keep startDate close to the last run and cap maxResults.

Input

Input fields

FieldTypeRequiredDefault/PrefillDescriptionExample
cikstringNoprefill 0000320193SEC Central Index Key (1-10 digits, leading zeros optional).0000320193
querystringNononeEDGAR full-text search query matched against filing documents.supply agreement
formTypesarray of stringNodefault ["10-K","10-Q","8-K"]Only return these SEC form types.["10-K","10-Q","8-K"]
startDatestringNononeInclusive lower bound for the filing date (YYYY-MM-DD).2026-01-01
endDatestringNononeInclusive upper bound for the filing date (YYYY-MM-DD).2026-10-17
maxResultsintegerNodefault 100, prefill 10, min 1, max 10000Maximum filings delivered to the dataset.10
monitorModebooleanNodefault true, prefill falseMonitor mode: filings already delivered to this Apify user for the same watch (issuer CIK or full-text query, with its form types) are not pushed again, so a scheduled run delivers only new filings. Disable for a one-off backfill; the Store default input disables it so the daily probe always sees filings.false

No field is required. If both cik and query are omitted, the run returns the latest filings of the example issuer (Apple Inc., CIK 0000320193).

Example input

The Store test input:

{"cik":"0000320193","formTypes":["10-K"],"maxResults":1}

Provide cik or query (at least one) for targeted monitoring. Full-text example with a bounded window:

{"cik":"0000320193","query":"supply agreement","formTypes":["8-K"],"startDate":"2026-10-01","endDate":"2026-10-17","maxResults":50}

Output

Example output

{
"accession_no": "0000320193-26-000081",
"cik": "0000320193",
"company_name": "Apple Inc.",
"form_type": "10-K",
"filing_date": "2026-10-02",
"report_date": "2026-09-27",
"acceptance_datetime": "2026-10-02T18:04:31.000Z",
"primary_document_url": "https://www.sec.gov/Archives/edgar/data/320193/000032019326000081/aapl-20260927.htm",
"is_amendment": false,
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019326000081/aapl-20260927.htm",
"scrapedAt": "2026-10-19T12:00:00.000Z"
}

url mirrors primary_document_url. report_date and acceptance_datetime are null when EDGAR does not return them; the Actor never invents timestamps.

Output fields

FieldTypeDescription
accession_nostringSEC accession number of the filing.
cikstringSEC Central Index Key, 10 digits with leading zeros.
company_namestringRegistered issuer (organisation) name.
form_typestringSEC form type, e.g. 10-K, 10-Q, 8-K or 10-K/A.
filing_datestring (date)Date the filing was accepted by EDGAR (YYYY-MM-DD).
report_datestring or null (date)Period covered by the filing, when provided.
acceptance_datetimestring or null (date-time)EDGAR acceptance timestamp in ISO 8601 UTC, when provided.
primary_document_urlstring (uri)Official EDGAR archive URL of the primary document.
is_amendmentbooleanTrue when the form type ends in /A.
urlstring (uri)Steadfetch envelope, same value as primary_document_url.
scrapedAtstring (date-time)Steadfetch envelope, ISO 8601 UTC timestamp of the run.

Pricing

Pay-per-event uses the two Apify synthetic events plus the reserved monitor-check event from .actor/pay_per_event.json:

  • apify-actor-start: 0.00005 USD per run (Apify-recommended default; includes the first 5 seconds of compute).
  • apify-default-dataset-item: 2.50 USD per 1,000 filings (0.0025 USD per filing), charged automatically for each validated filing saved to the default dataset. Measured cost per 1,000: below 0.10 USD (HTTP/JSON only, no browser and no proxy), leaving a gross margin of about 96%.
  • monitor-check: 1.00 USD per 1,000 checks (0.001 USD per checked record), charged in monitorMode only, once per record actually checked. A check that finds no change still bills the check but no result event.

The platform bills the synthetic events automatically, and the Actor calls Actor.charge() once per monitor run for the reserved monitor-check event (monitor mode only). Items that fail schema validation are not pushed and not billed; runs that return nothing only incur the start event.

Works on the Apify free plan - about 1,999 filings for the $5 monthly credit ((5.00 USD - 0.0002 USD run-start at the default 4 GB memory) / 0.0025 USD per filing).

Other Steadfetch Actors

FAQ

Does it need an API key? No. The EDGAR JSON endpoints are anonymous; the Actor declares a User-Agent with the Steadfetch contact mailbox, as the SEC access policy requires.

What is the request limit? At most 10 requests per second per IP, enforced by a sliding-window limiter with 429/403/5xx backoff.

Do I need both cik and query? No. Either is enough; providing both restricts the search to that CIK.

Does it collect personal data? No. Only filing metadata and issuer organisations are published; officer, signatory and contact fields are excluded and scrubbed before push (GDPR).

How are amendments handled? Forms ending in /A (for example 8-K/A) are returned when listed in formTypes and flagged with is_amendment: true.

Support

Report bugs through the Actor's Apify Store Issues tab or the Steadfetch Actors repository issues. Include the run ID and the exact input JSON so the failure can be reproduced.

Maintenance

Public in the Apify Store since 2026-10-20 and enabled for daily catalog QA (catalog registration; exact enable date not recorded). Daily catalog QA runs the default input, so the Actor is tested daily (2026-10-29). Schema and code tests run in CI on every push.