Skip to main content
The Audit API allows you to access comprehensive audit logs from . These logs provide detailed information about actions performed within the platform, including who performed the action, when it occurred, and other relevant details. This information is useful for maintaining security, compliance, and operational oversight. This guide will walk you through the steps to retrieve audit logs using the Audit API. The event types currently supported by the API are listed below. New event types are continually added as more areas of are integrated with the Audit API, and this list will be updated accordingly.
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:

Get the audit logs

Retrieve the audit logs using the Audit API. Base URL: GET /v1/events

Parameters

Example response

A successful response returns a 200 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 the product area that they relate to.

Account

Maia runner

Artifacts

Credentials

These events include those for secrets, cloud credentials, and OAuths.

Custom connector

Project

Project connection audit events are produced for SSH Tunnels, OAuths, and Secret definitions.

Environments

Environment connection audit events are produced for OAuths and Secret definitions.

Schedules

Streaming