Look up recently delisted entities
Updated
The GET /delisted endpoint returns entities that have recently been removed from their source lists. It is free and unauthenticated — no API token required. A browsable version of the same data is also published at compliapi.com/delisted.
When an entity is delisted, it immediately stops matching in screening calls. However, CompliAPI retains the record for audit history — so if you screened a wallet last month and it matched, you can still look up when it was removed and from which list. This is useful for due-diligence reviews, regulatory reporting, and confirming that a previously flagged entity is no longer designated.
How to use it
- Call
GET /api/v1/delistedwith no authentication header. - Optionally add
?limit=to control how many results are returned (between 1 and 500; default is 100). Results are ordered newest-first. - Optionally add
?lists=with a comma-separated set of list slugs to narrow the results to specific source lists. Slugs come fromGET /screen/lists.
# Most recent 100 delistings across all listscurl "https://api.compliapi.com/api/v1/delisted"
# Last 10 delistings from the OFAC SDN list onlycurl "https://api.compliapi.com/api/v1/delisted?limit=10&lists=ofac"
Understanding the response
Each entry includes the entity_type (onchain_address, email, website, or government_id), the value as it appeared on the list, the list slug, relevant metadata (such as the SDN name and programs), a source_url pointing to the original designation record, and a removed_at timestamp in UTC.
Tips and related features
- Delistings are not the same as never being listed. A
removed_atentry means the entity was formally designated and has since been removed — it still appears in your audit trail if you screened it while it was active. - For push notifications rather than polling, the monitoring webhooks feature fires an
entity.delistedevent whenever a value you are watching is removed from a list — no need to poll/delistedperiodically. - The
/delistedendpoint covers all lists CompliAPI tracks. If you only care about a subset, use the?lists=parameter to avoid noise from unrelated lists.