Start from the job, not from the endpoint.
Each page states the problem, why the filings alone make it work, the exact request that solves it, and what to know before you build on it.
Detect executive changes
Item 5.02 covers both an exit and a hire. Here is how to pull it and how to handle the half the code cannot answer.
See the call →Monitor bankruptcy and distress
The least ambiguous event on the form, plus the related codes that usually arrive before it.
See the call →Track delisting notices
The earliest public delisting signal, and the one event type our own study found the most in.
See the call →Watch merger activity
Items 2.01 and 5.01, plus an honest account of the deals that arrive under neither.
See the call →Find funding rounds early
The 15-day rule, the filters that matter, and the amount field that is not what it looks like.
See the call →Funding signals for sales
Dated, sourced, business-level triggers, and the compliance argument that comes with having no contact data at all.
See the call →No alerting, no scores, no advice.
You poll on your own schedule and build the workflow. Severity is a sorting aid a model assigned, the data is refreshed daily rather than streamed, and every record links back to the filing so the claim is checkable without us.
The guides cover the same ground from the pipeline side: parsing the XML, reading the item codes, and the fair access rules that apply either way.
Browse the guides →