List entries by request

The audit-trail entry point: returns the entries a given request or channel touched, in the
same envelope as the list endpoint. Answered from the append-only event log, so an entry a
later write re-stamped still answers to the earlier request id.

A page is counted in log entries rather than registry entries, so a page can come back
EMPTY while hasMore is true — iterate on hasMore, never stop on an empty page.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string

Matches an entry's last request id.

string

Matches an entry's last source, for example dsr, drop or cmp.

int32

Page size, 1-1000. Defaults to 100.

string

Opaque pagination token from a previous response. Do not construct or parse it.

Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json