Skip to main content
POST
Crypto Wallet Check
Check cryptocurrency wallet addresses against sanctions lists and risk databases. This endpoint validates wallet addresses and checks them against OFAC and other sanctions lists.

Endpoint

Authentication

Requires kyc:create permission. Include your Bearer token in the Authorization header.

Description

The crypto wallet check endpoint validates cryptocurrency wallet addresses and checks them against sanctions lists. It supports multiple blockchain networks and performs:
  1. Address Validation: Validates wallet address format for the specified network
  2. Sanctions Screening: Checks address against OFAC and other sanctions lists
  3. Risk Assessment: Identifies potential risks associated with the wallet
  4. Transaction History: Optional analysis of transaction patterns

Request Body Parameters

Zero Data Retention (ephemeral mode)

You can request ephemeral processing with either the X-Data-Retention: ephemeral header or "data_retention": "ephemeral" in the JSON body. Per-request ephemeral must be enabled for your account first: the endpoint identifier crypto.check (or the wildcard *) has to appear in your tenant’s data_processing_config.allowed_ephemeral_endpoints, otherwise the request is rejected with a 400. Tenants can also opt in account-wide by setting data_processing_config.mode to ephemeral — the tenant-level setting always wins over per-request flags and does not require the allowlist. Contact support to enable either option on your account. When ephemeral mode is active, the API returns the normal analysis response but does not store a validation record (nothing appears in the dashboard history) and does not emit the detailed audit event. The ephemeral flag also propagates to the internal sanctions lookups (target wallet and source wallets), which skip their own persistence. The platform retains only an aggregate billing metric (one counted crypto check, with no wallet address or outcome references); tenants with retain_billing_metrics: false suppress that too. An invalid data_retention value returns 400 before any quota is consumed.
The wallet analysis queries third-party blockchain APIs (e.g. TronGrid) to fetch transaction history; those providers process the wallet address under their own policies. Ephemeral mode guarantees zero retention in Legaltalent’s own stores.

Supported Networks

Request Example

Check Multiple Lists

Response Format

Success Response - No Match

Success Response - Match Found

Response Fields

Match Object

Error Responses

400 Bad Request - Invalid Address

400 Bad Request - Unsupported Network

400 Bad Request - Missing Parameters

Status Codes

Usage Examples

Python Example

JavaScript Example

Best Practices

  • Validate address format: Ensure wallet addresses match the expected format for the network
  • Check multiple lists: Use the lists parameter to check against multiple sanctions lists
  • Handle matches: Implement proper handling for matches found in sanctions lists
  • Network selection: Use the correct network code for the blockchain you’re checking
  • Error handling: Implement proper error handling for invalid addresses or network errors

Performance

  • Typical Response Time: 1-2 seconds
  • Rate Limits: Subject to API rate limiting (1,000 requests per 5 minutes)
  • Supported Networks: TRX (fully supported), BTC and ETH (partial support)

Integration Tips

  1. Address Validation: Validate address format client-side before submitting
  2. Network Detection: Automatically detect network based on address format when possible
  3. Batch Processing: For multiple addresses, make separate requests
  4. Error Handling: Handle network-specific errors appropriately