Address screening evaluations (history)
Changed onPages 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.
Request
- Base URLhttps://v3.euler.finance
- URLhttps://v3.euler.finance/v3/compliance/address-screening/evaluations
- Auth
- API key in header X-API-Key
- or HTTP bearer
Query parameters
Matches the requested or resolved chain of an evaluation, or the chain of a request.
Inclusive lower bound on the evaluation or request time (RFC 3339).
Inclusive upper bound on the evaluation or request time (RFC 3339).
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.
Page offset, capped at 10000 to bound query cost.
Response
Evaluations matching the filter.
Example response
{
"data": [
{
"provider": "trm"
}
]
}Changes
- info
added the optional property
/to the response with the status
- info
- warning
removed the optional property
/from the response with the status
- warning