SEC 8-K Item & Amendment Watch

Check a watchlist of companies for SEC 8-K and 8-K/A filing metadata. Get disclosed item codes, official document links, new/updated accession records and company-level source health in JSON or CSV. The starter preset includes Apple, Microsoft and NVIDIA; choose Only my CIKs to use your own list. No external API key is required.

This product helps maintain a disclosure-monitoring dataset. It reports filed metadata and does not assess an investment, infer a financial finding, summarize a filing's body, or claim that a disclosed event is materially significant.

Input example

{
  "preset": "starter",
  "lookbackDays": 180,
  "maxFilingsPerCompany": 10,
  "changesOnly": true,
  "monitorKey": "example"
}

Output and interpretation

Each successfully checked company produces a company_health row, including zero matching filings or zero new filings. That completed company check is billable. filing rows contain the accession number, form, filing/report dates, disclosed item codes, official source URL and initial/new/metadata_updated state.

8-K/A is marked as an amendment. Related original candidates share the CIK and reportDate within the retrieved recent data; this is candidate linkage, not a verified reference to a particular original filing. Missing dates remain null. Item 4.02 is labelled as a non-reliance disclosure code; the Actor makes no conclusion about a company's accounts.

Only the SEC recent submissions array is read. Historical archive files are not fetched. recentWindowCoversRequestedRange and resultLimitReached describe incomplete scope. The first run establishes a baseline; repeat runs suppress unchanged filing rows while still charging for each healthy company check. Absence never means a filing was deleted.

Fair access: requests are serial with at least one second between companies. 403/429 stops remaining company requests. No proxy rotation or access-control bypass is used. Keep one stream at a time and respect the SEC's aggregate fair-access limits; coverage and service availability are not guaranteed.

Official sources: SEC submissions APIs, fair-access policy, and reuse permissions. The official FAQ permits reuse of EDGAR public filing content. This Actor only processes corporate filing metadata, without retrieving contact details or document text.

Run and retrieve results

1. Open the Input tab, keep the example or add your own filters, then select Start. No operator approval is required.
2. Open Output for the results table. Export JSON through the dataset, or download RESULTS.csv from the run key-value store for spreadsheet-safe CSV.
3. Read OUTPUT for the authoritative records, source coverage, billing checkpoints and monitor storage ID. DIAGNOSTICS.json reports failures and caps.

The Actor uses limited permissions and stores its own monitor state in a named key-value store in your Apify account. Keep the same monitor name and semantic filters to compare runs; changing page/result limits does not reset the baseline. Each account has its own state. Run a single stream at a time: overlapping runs on the same monitor can repeat observations, and a detected conflicting state update is not overwritten. State keeps up to 3,000 filing fingerprints per company, with a 4 MiB overall monitor-state cap; very old evicted records may be observed again.

Pricing and spending limits

• Actor start: USD 0.01 for a run at the supported default 256 MB. Apify's start event is per GB with a one-event minimum, so larger memory settings can increase this charge.
• Company check: USD 0.025. One company whose official SEC recent submissions data passes validation, including zero matching or zero new filings. Source failures and schema errors are not charged.
• No separate dataset-item event. No proxy, AI API or paid external API is used.
• Set Maximum cost per run to cover the start and the number of checks/results you want. Budget caps can stop delivery early and are shown in OUTPUT.
• The start fee applies even if no match is found or the upstream service fails. Failed or undelivered outcomes do not incur the custom result/check event.

Results are saved before the custom outcome charge. A new run performs a new paid check; retrieve the old run before restarting it. The same run's uncertain dataset or charge POST is never intentionally repeated. If a charge is uncertain, processing stops with a billing audit instead of attempting a second charge. OUTPUT remains authoritative when dataset delivery is uncertain.

Data and support

Input, output and monitor state stay in your Apify account's storage under its retention policy. This Actor sends no messages, modifies no source data, and accepts no credentials or private source URLs. Source requests use an identifying User-Agent with the developer's public support profile.

Report reproducible defects in this Actor's Issues tab using a minimal invented example and the diagnostic code. Do not post API tokens or private run links.

Actual owner-validation output

Observed on 26 October 2026 (Japan time). This is a saved owner test, not a customer result or evidence of sales. Source data changes over time.

The saved run provided 3 healthy company checks and 16 filing records. The requested recent window was covered for the three checked companies. Its configured event total for an ordinary buyer at 256 MB would be USD 0.085, including startup. Owner event counts are validation, not paid customer revenue.

Abbreviated actual record:

{
  "companyName": "Apple Inc.",
  "form": "8-K/A",
  "accessionNumber": "0001140361-26-035325",
  "filingDate": "2026-09-01",
  "reportDate": "2026-04-17",
  "itemCodes": [
    "5.02"
  ],
  "isAmendment": true,
  "relatedOriginalCandidates": [],
  "sourceUrl": "https://www.sec.gov/Archives/edgar/data/320193/000114036126035325/ef20081427_8ka.htm"
}