SEC Form D Change Watch

Turn public U.S. private-offering filings into structured records you can check against the source. Retrieve issuer names, offering amounts, investor counts, and exact field differences between an amendment and its named SEC comparator.

Use it for a research spreadsheet, a filing-review queue, or a recurring data pipeline. Every record includes the original SEC XML link and an explicit review flag.

Run a search

Choose a date window of up to seven calendar days and a maximum of 1-100 filings:

{"dateFrom":"2026-09-04","dateTo":"2026-09-04","maxResults":10}

Export the resulting Dataset as JSON or CSV, or call the Actor through Apify's API. No SEC credentials or enrichment subscription is needed.

Coverage limit: this first release retrieves at most the selected number of source filings. It does not paginate an entire busy date window. Check secSearchTotal and secSearchTruncated in the run's OUTPUT record before interpreting the results as complete. A short returned page or a lower-bound search total is flagged as incomplete, even when the requested cap is higher.

What each record contains

• Public primary issuer name and CIK, checked against the filing reference.
• Filing date, accession number, SEC file number, XML URL, and content hash.
• Reported offering amount, amount sold, remaining amount, investor count, industry group, and first-sale date.
• Literal amounts such as Indefinite alongside numeric values where available.
• Exact comparator accession, changed field names, numeric differences, and review flags.

One source-verified example from September 4, 2026 is Broken Bow Capital Fund LLC-Series 1, accession 0002153883-26-000001, reporting $3,600,000 sold and an indefinite offering amount. This is an example of reported source data, not an investment recommendation.

Understand amendment comparisons

An amendment is compared only with the exact previousAccessionNumber named in its XML. That may be the original filing rather than the immediately preceding amendment. An amount difference therefore does not establish how much was raised between consecutive filings.

AMENDMENT_CHANGED means one of the captured fields differs. An unchanged comparison returns VALIDATED_AMENDMENT_NO_FIELD_CHANGE. Missing or incompatible references return AMENDMENT_UNRESOLVED. Additional references in clarification text set reviewRequired without declaring a conflict. Issuer names alone are never used to join offerings.

Inspect a real Form D/A review example

For a filing-review queue, check the exact XML comparison before interpreting an amendment as a new funding event. These two September 4, 2026 filings were replayed through the current comparison code against live SEC XML:

Filed issuer	Compared source	Observed result	Charge eligible
Glade Brook Private Investors XXVII LP	Amendment and its named 2021 comparator	Both report $2,200,000 sold and 8 investors. Captured fields are unchanged, but the clarification includes another accession: reviewRequired: true.	No
MY Japan Focused Fund Ltd	Amendment and its named 2021 comparator	First-sale date, amount sold, and investor count differ; AMENDMENT_CHANGED, reviewRequired: false. The amount comparison is against the named 2021 record.	Yes

Open both official links, compare the recorded values, then inspect changedFields, numericDeltas, and additionalAccessionReferences in your output. Source hashes let you identify the exact XML bytes used. A review flag calls attention to the evidence; the tool does not decide whether a filing is legally sufficient or whether another amendment is required.

These are source examples, not a guarantee that a capped date search will include these particular records. The current public input accepts a date window and result cap; it does not yet support targeting an accession or issuer. Set a run charge limit before expanding the cap.

Billing and failures

The price is $0.10 per validated original filing or unambiguous amendment change, with platform usage included. There is no startup charge. Set a maximum charge for each run in Apify; the Actor stops publishing when that limit is reached.

No-change, unresolved, review-required, duplicate, or failed records do not trigger the custom charge. The bounded source set is validated before output begins. Source failures stop the run. Only a valid search response explicitly confirming zero matches reports NO_MATCHES, with zero output and charges. Malformed results, timed-out searches and failed search shards report SOURCE_FAILURE; they are never treated as evidence that no filings exist.

Reliability and support

This release completed a real Apify cloud run with ten source-validated original filings. Separate local checks exercised two real amendments; automated tests cover historical comparator lookup, invalid XML, issuer mismatches, caps, and billing eligibility. Source requests are paced at no more than one per second per run and include a descriptive contact User-Agent.

Use the Actor's Issues tab for support. Include the run ID and expected result. Do not include credentials or private documents. This tool provides public filing data; it does not evaluate investments or collect individual contact details.