TRM Labs
The TRM Labs adapter is implemented for address sanctions screening.
Implementation
Section titled “Implementation”| Field | Value |
|---|---|
| Integration name | trmlabs |
| Display name | TRM Labs |
| Type | sanctions |
| Required credentials | apiKey |
| Base URL | https://api.trmlabs.com |
| Endpoint path | /public/v1/sanctions/screening |
| Timeout | 10 seconds |
| Retries | 3 attempts |
Screening
Section titled “Screening”The adapter supports:
- Address screening through the TRM Labs sanctions screening endpoint
- Retry on non-terminal failures
A response that names the screened address and says whether it isSanctioned is a successful check, and the vendor's raw response is stored with it. A response that does not is INVALID_RESPONSE.
Transaction hashes are not screened: a transaction check fails with UNSUPPORTED_OPERATION, since the TRM Sanctions API screens addresses.
Credential Behavior
Section titled “Credential Behavior”The adapter uses the API key saved for the transfer's environment. Without one, a check fails before any request is sent, and the connection test with a missing-credential error. There is no sandbox fallback.
Error Mapping
Section titled “Error Mapping”The adapter maps common HTTP responses to stable error codes:
| HTTP Status | Error Code |
|---|---|
400 |
BAD_REQUEST |
401 |
UNAUTHORIZED |
403 |
FORBIDDEN |
404 |
NOT_FOUND |
429 |
RATE_LIMITED |
5xx |
SERVICE_UNAVAILABLE |
| Any other | HTTP_ERROR |