Check a crypto address against OFAC
Checking an address against OFAC tests it against the SDN designations. The sanctions endpoint returns a boolean match and the list name when flagged. Store each check so an OFAC designation can be evidenced at the moment it was found.
- A live API key with AML scope.
- The address and chain path segment to check.
1Query the sanctions endpoint
GET the sanctions path for the address. The sanctions data set includes the OFAC SDN list. This is a C2 call.
curl https://api.1st-node.com/v1/aml/eth/0x8589.../sanctions \ -H "Authorization: Bearer sk_live_..."
2Read the match and list
A clean address returns match false. An OFAC hit returns match true with the list name identifying the SDN designation.
> { "match": true, "list": "OFAC SDN", "entity": "designated-address" }3Block and record on a hit
Any OFAC match is a hard stop. Reject the transaction, freeze the interaction, and store the response so the block is evidenced.
Frequently asked
Does the sanctions endpoint cover lists beyond OFAC?
Yes. The list field names the specific source of a match, of which OFAC SDN is one. Read that field rather than assuming the source.
How long should an OFAC check be retained?
Retain the response for the period your compliance policy requires. The stored result is the evidence that the check was performed at that time.
Keep reading
Top up, get a key, ship.
Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.
Get API key