Skip to main content
GET
Check if Wallet Address is Sanctioned
Checks whether a given address is directly listed on an official sanctions list, including OFAC. This endpoint returns true only for an exact address match; addresses merely associated with a sanctioned entity will return false. To identify indirect sanctions exposure or entity associations, use the main risk intelligence endpoint.

Authorizations

x-api-key
string
header
required

Path Parameters

walletAddress
string
required

Query Parameters

chain
enum<string>
required

Selected chain. Supported values: 'eth', 'base', 'bsc', 'pol', 'opt', 'arb', 'sol', 'btc', 'tron', 'stellar', 'robinhood', and 'hedera'. TRON addresses must be valid base58check (34 chars, leading 'T').

Available options:
eth,
base,
bsc,
pol,
opt,
sol,
arb,
btc,
tron,
stellar,
hedera,
robinhood

Response

Success. If authoritative screening is unavailable, a fail-open deployment returns sanctions_status: unknown; a fail-closed deployment returns 503 instead.

address
string
required
is_sanctioned
boolean
required
sanctions_status
enum<string>
required

Address-screening verdict for this operation, not the RWA token-attribute sanctions_status vocabulary (none | proposed | designated). Callers should require clean before treating an address as cleared; unknown means an authoritative screening result could not be obtained.

Available options:
sanctioned,
clean,
unknown

True when the address is attributed to an entity subject to sanctions but is not itself named on a sanctions list. Independent of is_sanctioned and sanctions_status, which reflect list matches only. Stays false when sanctions_related_status is unknown.

Attribution check for this address. related and not_related mean the attribution data was read; unknown means it could not be read, so the address could not be cleared of attribution. Callers should gate on this field rather than on is_sanctions_related === false.

Available options:
related,
not_related,
unknown
check_id
string<uuid>
required

Id of this check. Same value as the X-Request-Id response header. Keep it with the result as an audit reference.

Example:

"3f1c2b9e-7a4d-4e1b-9c55-0d6a2f8e4b71"

checked_at
string<date-time>
required

When this response was served (ISO 8601, UTC). A cached result is served now, so this is the time of your request.

Example:

"2026-11-03T14:02:11.482Z"

data_as_of
string<date-time> | null
required

When the result was computed (ISO 8601, UTC). Earlier than checked_at when the result came from cache. null when the compute time is unknown, for example on a pending (202) answer.

Example:

"2026-11-03T14:02:11.482Z"