Compliance

Address screening evaluations (history)

Changed on

Pages through the retained provider evaluations, newest first, including the raw provider payload and the screened address. Requires an active, unexpired API key with the compliance:screening-read capability, a separate grant from compliance:screen, or a platform session whose operator is on the admin allowlist (the Toolbox). Responses are compliance data: Cache-Control: no-store, never log them. suspicious=true|false keeps one verdict. A query parameter this route does not list answers 400 VALIDATION_ERROR.

get/v3/compliance/address-screening/evaluations

Request

  • Base URL
    https://v3.euler.finance
  • URL
    https://v3.euler.finance/v3/compliance/address-screening/evaluations
  • Auth
    • API key in header X-API-Key
    • or HTTP bearer

Query parameters

addressstring
chainstring

Matches the requested or resolved chain of an evaluation, or the chain of a request.

fromstring date-time

Inclusive lower bound on the evaluation or request time (RFC 3339).

tostring date-time

Inclusive upper bound on the evaluation or request time (RFC 3339).

suspicious'true' | 'false'

true for the evaluations that flagged the address, false for the clear ones; absent for both. Applied before paging, so meta.total counts the matching evaluations.

limitinteger
offsetinteger

Page offset, capped at 10000 to bound query cost.

Response

Evaluations matching the filter.

Example response

{
  "data": [
    {
      "provider": "trm"
    }
  ]
}

Changes