sapi
Successful API Operation Only emitted by the Management API on POST, DELETE, PATCH, and PUT
Client name associated with the client_id, when available. May be empty string.
Description of the event. This can also contain a description of the issue for failure logs.
Log details
The name of the environment where the event occurred
"prod-eu-1"
"prod-us-1"
The IP address associated with the request. For an auth related log this should be the end user IP. For a machine-to-machine auth flow this should be the IP of the computer doing the authentication. For management logs like sapi and mgmt_api_read this should be the IP of the admin using the manage dashboard.
Log id
Tenant name
Successful API Operation
"sapi"Event schema meta
The client or SDK used to do this request, if any. This is based on the Auth0-Client HTTP header.
Client related to the API call. Clients are also called applications. The underlying application may not be owned by your tenant and may not be accessible. For failure logs, this may be a valid ID, an invalid one, or any ID.
The date when the event occurred in ISO 8601 format
"2024-01-15T10:30:00.000Z"
Whether the request originated from a mobile device. Only present when user_agent is available.
References for correlating related events across services and stitching them into distributed traces.
The user_agent behind this log, when available
"Chrome 120.0.0 / Mac OS X 10.15.7"
ID of the user executing the action, when available. For machine to machine auth flows, this field may contain an empty string.