Find the release, then read it
GET /v1/events/enforcement turns three SEC enforcement release feeds into one filtered list. It is useful when a research, compliance, or diligence process needs to find the relevant release quickly and keep its SEC URL with the result.
The endpoint is a research index, not a finding of liability. A respondent name can be ambiguous, a dollar amount can be absent or refer to only one component of relief, and an issuer mentioned in a release is not necessarily the respondent. Read the linked SEC release before using a result in an investment or compliance decision.
Sources and fields
The API returns records from:- SEC litigation releases (
litigation_release) - SEC administrative proceedings (
administrative_proceeding) - Accounting and Auditing Enforcement Releases (
aaer)
violationType is a routing label inferred from release language; it is not an SEC legal classification.
Start with a narrow question
requestId when troubleshooting and use nextCursor only when hasMore is true.
Filters
| Parameter | Use it for |
|---|---|
query | Matching release titles and descriptions. |
source_type | Restricting the source to litigation_release, administrative_proceeding, or aaer. |
violation_type | One normalized label: fraud, insider_trading, reporting_violation, market_manipulation, registration_violation, investment_adviser, broker_dealer, municipal_securities, or other. |
respondent, ticker, cik | Focusing the release search on a person or issuer. Entity matches should be checked against the linked source. |
penalty_min, penalty_max | Narrowing on a disclosed dollar amount when one was parsed. |
date_from, date_to | Restricting SEC publication dates with inclusive YYYY-MM-DD bounds. |
limit, cursor | Paging through a bounded result set. limit is 1–50. |
A practical review loop
- Filter by the person, issuer, source type, or risk question you are investigating.
- Read
title,excerpt,respondents, andviolationTypeas a triage layer. - Open
documentUrl; it is the evidence for the record. - Preserve the release URL and
requestIdwith downstream research instead of treating the normalized label as the complete story.

