Compliance

Address screening request audit log (history)

Changed on

Pages through the append-only request audit log, newest first: which key asked, for which address and chain, whether a cached evaluation was reused, and how rejected or failed requests ended. Requires the compliance:screening-read capability or an allowlisted platform session. Responses are compliance data: Cache-Control: no-store, never log them. Each completed request records the verdict it returned and, when a waiver cleared a flagged evaluation, the change that granted it. There is no suspicious filter here: it answers 400 VALIDATION_ERROR, like any query parameter this route does not list.

get/v3/compliance/address-screening/requests

Request

  • Base URL
    https://v3.euler.finance
  • URL
    https://v3.euler.finance/v3/compliance/address-screening/requests
  • 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).

limitinteger
offsetinteger

Page offset, capped at 10000 to bound query cost.

Response

Request audit rows matching the filter.

Changes

    • info

      added the required property // to the response with the status

    • info

      added the required property // to the response with the status

    • info

      added the optional property / to the response with the status