Audit logs contain user identifiers, such as name and email address, to attribute actions to specific users. Only users with the View Audit Events permission can access audit logs. Logs are retained within the platform, and are accessible via and the Audit API for a rolling 90-day period. Events older than 90 days aren’t available via the platform or API, even though underlying audit data may be stored for up to 12 months for operational purposes.
Prerequisites
Before you begin, make sure you have the following:- A account.
- Valid API credentials for API access.
- An access token with the required privileges (refer to Authentication and Get the access token).
Get the audit logs
Retrieve the audit logs using the Audit API. Base URL:GET /v1/events
Parameters
Example response
A successful response returns a200 OK status code and a JSON body containing the audit logs, as in the following example:
Audit event types
The following tables list the event types currently supported by the Audit API. Events are grouped by scope, and then by the product area that they relate to.Scope - Account
Account
Maia runner
Custom connector
Scope - Project
Project
Project connection audit events are produced for SSH Tunnels, OAuths, and Secret definitions.
Artifacts
Credentials
These events include those for secrets, cloud credentials, and OAuths.Schedules
Streaming
Scope - Environment
Environments
Environment connection audit events are produced for OAuths and Secret definitions.
