US Enforcement & Disciplinary API

Base URL: https://api.techcompass.com.au — SEC litigation releases and FINRA BrokerCheck data with KYC risk signals.

About this Dataset

The US Enforcement & Disciplinary API aggregates regulatory enforcement and disciplinary action data from two independent US financial regulators: the Securities and Exchange Commission (SEC) and the Financial Industry Regulatory Authority (FINRA). Together they cover the complete landscape of US securities law enforcement against individuals and firms.

SEC Enforcement — Litigation Releases

The SEC’s Litigation Releases are the formal public record of every civil enforcement action brought by the Commission in the US district courts. They cover securities fraud, insider trading, Ponzi schemes, unregistered offerings, and market manipulation — with electronic records dating back to 1995.

Each release includes: case title, respondent names, filing date, case type classification, and a direct URL to the full text on SEC.gov. Tech Compass indexes this data and provides full-text search against respondent names, enabling rapid cross-referencing of any individual or entity against the SEC’s enforcement history.

Use cases: Pre-engagement due diligence on investment managers, counterparty vetting, legal background checks, regulatory compliance screening.

FINRA BrokerCheck

FINRA BrokerCheck is the authoritative public database of all broker-dealers and individual financial professionals registered with FINRA — the self-regulatory organisation that oversees US broker-dealers under SEC oversight. It covers over 600,000 currently registered and 1.3 million formerly registered individuals.

Each record includes: registration status, current and past employers, licensing (Series 6, 7, 63, 65, 66, and 30+ other FINRA examinations), state registrations, and the complete disclosure history — customer complaints, regulatory actions, civil judgements, and criminal matters.

Use cases: Broker verification before account opening, ongoing registered representative monitoring, AML/KYC due diligence on financial intermediaries, regulatory compliance documentation.

Data Terms

SEC Enforcement data is US Government public domain. BrokerCheck data is provided under written confirmation from FINRA (Case #CAS-2946202-V7L1H3, 11 May 2026) — commercial redistribution permitted for compliance API platforms with source attribution. Attribution is included in data_lineage on every FINRA response.


Authentication

All endpoints require an API key in the Authorization header:

Authorization: ApiKey tc_live_<your_key>

Keys beginning with sk_live_ (issued before May 2026) remain valid. New keys use the tc_live_ prefix. Obtain a key at signup.

Tiers

TierCalls/monthPrice
Free10,000$0
Professional500,000USD $1,500/mo or AUD $2,250/mo
EnterpriseUnlimitedContact sales

Rate limit headers

HeaderDescription
X-RateLimit-LimitMonthly quota for your tier
X-RateLimit-RemainingCalls remaining this month
X-RateLimit-ResetUTC Unix timestamp when quota resets

Common Response Structure

All enforcement endpoints return a consistent envelope:

{
  "data": { ... },
  "meta": {
    "request_id": "a1b2c3d4-...",
    "cached": false,
    "timestamp": "2026-06-19T07:00:00Z"
  },
  "data_lineage": {
    "source": "FINRA BrokerCheck",
    "source_url": "https://brokercheck.finra.org/individual/128760",
    "license_url": "https://brokercheck.finra.org/terms",
    "retrieved_at": "2026-06-19T07:00:00Z",
    "compiled_at": "2026-06-19T06:00:00Z",
    "request_id": "a1b2c3d4-...",
    "downstream_use_restriction": "compliance and regulatory purposes only"
  },
  "kyc": {
    "overall_risk": "HIGH",
    "flags": ["BARRED"]
  }
}

SEC responses use a simpler lineage block (no compiled_at or downstream_use_restriction):

{
  "data_lineage": {
    "source": "SEC Enforcement — Litigation Releases",
    "source_url": "https://www.sec.gov/enforcement-litigation/litigation-releases",
    "retrieved_at": "2026-06-19T07:00:00Z",
    "request_id": "a1b2c3d4-..."
  }
}

KYC Signal Reference

Every FINRA endpoint returns a kyc block with overall_risk and flags. Use this to automate onboarding decisions.

Individual broker KYC signals

ConditionFlagRisk Level
permanent_bar = trueBARREDHIGH
registration_status = "Not currently registered" AND has_disclosures = trueNOT_REGISTERED_WITH_DISCLOSURESMEDIUM
registration_status = "Not currently registered" AND has_disclosures = falseNOT_REGISTEREDMEDIUM
has_disclosures = true (registered)HAS_DISCLOSURESMEDIUM
Registered, no disclosuresLOW

Firm KYC signals

ConditionFlagRisk Level
expelled_date is presentEXPELLEDHIGH
Firm not in FINRA recordsNOT_FOUNDMEDIUM
has_disclosures = true (active firm)HAS_DISCLOSURESMEDIUM
Active, no disclosuresLOW

FINRA Data Terms

Downstream use restriction: FINRA BrokerCheck data may only be used for compliance and regulatory purposes. This field appears in data_lineage.downstream_use_restriction in every FINRA response. By using these endpoints you agree to the FINRA BrokerCheck Terms of Service.

The data_lineage.compiled_at field records when FINRA compiled the BrokerCheck dataset — required for regulatory audit trails.

Error Reference

StatusMeaning
400Invalid parameters (e.g. query too short)
401Missing or invalid API key
403API key does not have access to product us_enforcement
404CRD number or release number not found
429Monthly quota exhausted
503FINRA BrokerCheck temporarily unavailable

SEC Enforcement Endpoints

Search SEC litigation releases by respondent name and/or date range. Returns up to 200 results ordered by date descending.

ParameterRequiredDescription
entityNoRespondent name to search for (case-insensitive partial match against summary and respondents)
date_fromNoStart date YYYY-MM-DD
date_toNoEnd date YYYY-MM-DD
limitNoMax results (default: 50, max: 200)
curl "https://api.techcompass.com.au/v1/us/enforcement/sec?entity=Enron&date_from=2001-01-01&date_to=2005-12-31" \
  -H "Authorization: ApiKey tc_live_<your_key>"
{
  "data": {
    "query": "Enron",
    "count": 14,
    "results": [
      {
        "release_number": "LR-18174",
        "release_date": "2003-06-25",
        "respondents": ["Enron Corp", "Jeffrey K. Skilling"],
        "summary": "SEC charges Enron Corp and former CEO Jeffrey Skilling...",
        "url": "https://www.sec.gov/litigation/litreleases/lr18174.htm",
        "fetched_at": "2026-06-19T06:00:00Z"
      }
    ]
  },
  "meta": { "request_id": "a1b2c3d4-..." },
  "data_lineage": {
    "source": "SEC Enforcement — Litigation Releases",
    "source_url": "https://www.sec.gov/enforcement-litigation/litigation-releases",
    "retrieved_at": "2026-06-19T07:00:00Z",
    "request_id": "a1b2c3d4-..."
  }
}

Errors: 400, 401, 403, 429

GET /v1/us/enforcement/sec/{release_number}

Retrieve a specific SEC litigation release. Accepts any of these formats: LR-26551, 26551, lr-26551.

ParameterDescription
release_numberSEC litigation release number. Prefix LR- applied automatically if omitted.
curl "https://api.techcompass.com.au/v1/us/enforcement/sec/LR-26551" \
  -H "Authorization: ApiKey tc_live_<your_key>"

Errors: 401, 403, 404, 429


FINRA BrokerCheck Endpoints

GET /v1/us/enforcement/finra/broker/{crd_number}

Look up an individual broker by FINRA CRD number. Returns registration status, all name aliases, disclosure count, and a KYC risk assessment.

ParameterDescription
crd_numberFINRA Central Registration Depository number (numeric string)
curl "https://api.techcompass.com.au/v1/us/enforcement/finra/broker/4728166" \
  -H "Authorization: ApiKey tc_live_<your_key>"
{
  "data": {
    "crd_number": "4728166",
    "record_type": "individual",
    "individual_name": "Ernie Preston Simmons III",
    "other_names": [],
    "registration_status": "Not currently registered",
    "permanent_bar": true,
    "has_disclosures": true,
    "bc_scope": true,
    "ia_scope": false,
    "sec_number": null,
    "current_employments": []
  },
  "meta": { "request_id": "b2c3d4e5-..." },
  "data_lineage": {
    "source": "FINRA BrokerCheck",
    "source_url": "https://brokercheck.finra.org/individual/4728166",
    "license_url": "https://brokercheck.finra.org/terms",
    "compiled_at": "2026-06-19T06:00:00Z",
    "retrieved_at": "2026-06-19T07:00:00Z",
    "request_id": "b2c3d4e5-...",
    "downstream_use_restriction": "compliance and regulatory purposes only"
  },
  "kyc": {
    "overall_risk": "HIGH",
    "flags": ["BARRED"]
  }
}

Errors: 401, 403, 404, 429, 503

GET /v1/us/enforcement/finra/firm/{crd_number}

Look up a registered firm by FINRA CRD number. Returns registration status, name aliases, expelled date (if applicable), and KYC risk.

ParameterDescription
crd_numberFINRA Central Registration Depository number for the firm
curl "https://api.techcompass.com.au/v1/us/enforcement/finra/firm/13992" \
  -H "Authorization: ApiKey tc_live_<your_key>"
{
  "data": {
    "crd_number": "13992",
    "record_type": "firm",
    "firm_name": "All-Tech Direct, Inc.",
    "other_names": ["All Tech Direct"],
    "registration_status": "Not currently registered",
    "expelled_date": "2001-07-31",
    "has_disclosures": true,
    "bc_scope": true,
    "ia_scope": false,
    "sec_number": "8-43302"
  },
  "kyc": {
    "overall_risk": "HIGH",
    "flags": ["EXPELLED"]
  }
}

Errors: 401, 403, 404, 429, 503

Cross-source enforcement search. Searches both SEC litigation releases and FINRA BrokerCheck in a single call. For numeric queries, also attempts FINRA CRD lookup.

ParameterRequiredDescription
qYesName, CRD number, or release number (min 2 chars)
typeNoFilter: individual | firm | sec | all (default)
curl "https://api.techcompass.com.au/v1/us/enforcement/search?q=4728166&type=individual" \
  -H "Authorization: ApiKey tc_live_<your_key>"

Errors: 400, 401, 403, 404, 429, 503


Known Test CRDs & Release Numbers

Use these for integration testing. All values are real public FINRA and SEC records.

CRD / ReleaseTypeEntityExpected KYC
128760IndividualDi Ves Tech (representative)LOW — Registered
162948FirmTechstarsLOW — Active
7691FirmMerrill Lynch, Pierce, Fenner & Smith Inc.LOW — Active, large firm
13992FirmAll-Tech Direct, Inc.HIGH — EXPELLED
4728166IndividualErnie Preston Simmons IIIHIGH — BARRED
LR-18174SEC releaseEnron Corp / Jeffrey Skilling

Common Use Cases

1. Pre-onboarding broker background check

Who uses this: Compliance teams at banks, fintechs, and asset managers screening financial professionals before engagement.

curl "https://api.techcompass.com.au/v1/us/enforcement/finra/broker/128760" \
  -H "Authorization: ApiKey YOUR_API_KEY"
What to look for: kyc.overall_risk should be LOW for clean registered brokers. Check data.permanent_bar explicitly — it maps to HIGH risk. Gotcha: A broker may appear registered but have historical disclosures — always check data.has_disclosures as well.

2. Firm due diligence before counterparty engagement

Who uses this: Risk teams evaluating broker-dealers, RIAs, and investment firms before entering into business relationships.

curl "https://api.techcompass.com.au/v1/us/enforcement/finra/firm/7691" \
  -H "Authorization: ApiKey YOUR_API_KEY"
What to look for: data.expelled_date — if present, the firm was expelled from FINRA and kyc.overall_risk will be HIGH. Check data.other_names for historical firm names that may appear in contracts or correspondence.

3. SEC enforcement action lookup for a specific entity

Who uses this: Legal teams and compliance officers checking whether a counterparty has been the subject of SEC enforcement action.

curl "https://api.techcompass.com.au/v1/us/enforcement/sec?entity=Enron&date_from=2001-01-01" \
  -H "Authorization: ApiKey YOUR_API_KEY"
Gotcha: This endpoint searches the summary text and respondents array — it does not use structured entity matching. A search for "Goldman" will return any release mentioning Goldman Sachs. Use date_from and date_to to narrow results for active monitoring workflows.

4. Ongoing counterparty monitoring (cross-source)

Who uses this: AML and compliance teams monitoring known counterparties for new enforcement actions.

curl "https://api.techcompass.com.au/v1/us/enforcement/search?q=4728166" \
  -H "Authorization: ApiKey YOUR_API_KEY"
What to look for: The sources array in the response shows which sources returned results (SEC, FINRA, or both). For CRD-based queries, both FINRA individual and firm records are checked automatically when type=all.

Data Sources

SourceLicenceRefresh
SEC Enforcement — Litigation ReleasesUS Government Public DomainDaily at 06:00 UTC via SEC RSS feed
FINRA BrokerCheckPermitted use: compliance/regulatory purposes only. See brokercheck.finra.org/termsOn-demand via FINRA API; response cached per CRD for 24 hours

About this API

What this API does

The Tech Compass US Enforcement & Disciplinary API provides programmatic access to SEC litigation releases and FINRA BrokerCheck registration data, returning structured KYC risk signals for compliance workflows. It covers individual broker registration status (including permanent bars and disclosures), firm registration and expulsion history, and SEC enforcement actions against named respondents — all with immutable audit logging and a consistent data_lineage block per call.

Who uses this API

  • Compliance officers at banks, broker-dealers, and asset managers
  • AML/KYC teams building automated onboarding screening
  • Fintech engineers integrating enforcement checks into onboarding flows
  • Legal teams performing due diligence on financial counterparties
  • Risk teams monitoring existing counterparty relationships
  • RegTech platforms building compliance-as-a-service products

Key use cases

  • Pre-onboarding broker screening — verify registration status and check for permanent bars before engaging a financial professional
  • Firm counterparty due diligence — check whether a broker-dealer or RIA has been expelled from FINRA
  • SEC enforcement history lookup — search litigation releases by respondent name and date range
  • Ongoing monitoring — poll for new SEC enforcement actions against known counterparties
  • Automated KYC decisioning — use the kyc.overall_risk field to gate manual review workflows
  • Audit trail generation — every call creates an immutable audit log entry with request_id for regulatory reporting

Applicable compliance frameworks

  • FINRA Rule 2010 (Standards of Commercial Honor and Principles of Trade)
  • SEC Rules of Practice — enforcement and disciplinary actions
  • US Bank Secrecy Act (BSA) — AML due diligence obligations
  • FinCEN CDD Rule — beneficial ownership and key control person checks
  • APRA CPS 234 — third-party information security risk (for AU-regulated entities)
  • AU AML/CTF Act 2006 — AUSTRAC KYC obligations for reporting entities

Data sources

Frequently asked questions

How current is the FINRA BrokerCheck data?
FINRA BrokerCheck data is fetched on-demand for each unique CRD number and cached for 24 hours. The data_lineage.compiled_at field shows when FINRA compiled the underlying dataset — this is FINRA's own timestamp, not the cache time. For time-sensitive compliance decisions, verify against BrokerCheck directly.
How current is the SEC litigation release data?
The SEC enforcement pipeline runs daily at 06:00 UTC and fetches the full RSS feed from SEC.gov. New releases typically appear within 24 hours of SEC publication.
Is every API call audited?
Yes. An immutable audit log entry is written before every response is returned. The meta.request_id in the response matches the audit log entry and can be used for regulatory reporting.
Can I use FINRA BrokerCheck data for marketing purposes?
No. FINRA's terms permit use for compliance and regulatory purposes only. This restriction is reflected in data_lineage.downstream_use_restriction on every FINRA response. By calling these endpoints you agree to the FINRA BrokerCheck Terms of Service.
What SLA is available?
Professional and Enterprise tier subscribers receive SLA documentation on request. Contact [email protected] for details.

Related APIs