audit
A single item in the audit log represents both the beginning and end of the logged operation (represented by time_started and time_completed) so that clients do not have to find multiple entries and match them up by request ID to get the full picture of an operation. Because timestamps may not be unique, entries have also have a unique id that can be used to deduplicate items fetched from overlapping time intervals.
Audit log entries are designed to be immutable: once you see an entry, fetching it again will never get you a different result. The list is ordered by time_completed, not time_started. If you fetch the audit log for a time range that is fully in the past, the resulting list is guaranteed to be complete, i.e., fetching the same timespan again later will always produce the same set of entries.
Query Parameters
Exclusive
Maximum number of items returned by a single call
Token returned by previous call to retrieve the subsequent page
Supported set of sort modes for scanning by timestamp and ID
Required, inclusive
Responses
list of items on this page of results
Audit log entry
How the user authenticated the request. Possible values are "session_cookie" and "access_token". Optional because it will not be defined on unauthenticated requests like login attempts.
Unique identifier for the audit log entry
API endpoint ID, e.g., project_create
Request ID for tracing requests through the system
URI of the request, truncated to 512 characters. Will only include host and scheme for HTTP/2 requests. For HTTP/1.1, the URI will consist of only the path and query.
Result of the operation
Result of an audit log entry
IP address that made the request
Time operation completed
When the request was received
User agent string from the request, truncated to 256 characters.
token used to fetch the next page of results (if any)