> For the complete documentation index, see [llms.txt](https://run-ai-docs.nvidia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://run-ai-docs.nvidia.com/multi-tenant/infrastructure-setup/procedures/event-history.md).

# Audit Logs API

This section provides details about NVIDIA Run:ai’s Audit log.

The NVIDIA Run:ai control plane provides the audit log API to reflect the information regarding changes to business objects: clusters, projects and assets etc. Go to the [Audit Logs](https://run-ai-docs.nvidia.com/multi-tenant-api/audit/auditlogs) API reference to view the available actions. Since the amount of data is not trivial, the API is based on paging. It retrieves a specified number of items for each API call. You can get more data by using subsequent calls.

{% hint style="info" %}
**Note**

Only system administrator users with tenant-wide permissions can access Audit log.
{% endhint %}

## Retrieve Audit Logs

You can retrieve audit logs programmatically to track tenant-related operations, user actions, and system changes across their managed environment.

### Define Query Parameters

Use the following optional parameters to filter results:

* `startTime` / `endTime` - ISO 8601 format (e.g., `2024-06-01T00:00:00Z`)
* `eventTypes` - Filter specific event types (e.g., `CREATE`, `DELETE`, `LOGIN`)
* `resourceTypes` - Filter by resource type (e.g., `TENANT`, `CLUSTER`, `USER`)
* `userIds` - Filter by one or more user IDs
* `page` / `pageSize` - Paginate results
* `sort` – `asc` or `desc`

### Send the API Request

```bash
curl -L 'https://console.<DOMAIN>/api/v1/audit-logs' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'Content-Type: application/json' \
  -G \
  --data-urlencode "startTime=2024-06-01T00:00:00Z" \
  --data-urlencode "endTime=2024-06-08T00:00:00Z" \
  --data-urlencode "resourceTypes=TENANT,CLUSTER" \
  --data-urlencode "eventTypes=CREATE,DELETE" \
  --data-urlencode "sort=desc"
```

Each entry contains metadata about the action:

* `timestamp`
* `eventType`
* `resourceType` and `resourceId`
* `userId` who initiated the action
* `details` describing the change

**Example Response**

```json
{
  "items": [
    {
      "timestamp": "2024-06-08T10:30:00Z",
      "eventType": "CREATE",
      "resourceType": "TENANT",
      "resourceId": "tenant-a",
      "userId": "admin@hostorg.com",
      "details": "Tenant created via Management Interface API"
    },
    {
      "timestamp": "2024-06-07T12:15:00Z",
      "eventType": "DELETE",
      "resourceType": "CLUSTER",
      "resourceId": "cluster-b",
      "userId": "ops@hostorg.com",
      "details": "Cluster deleted via host org automation"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 2
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://run-ai-docs.nvidia.com/multi-tenant/infrastructure-setup/procedures/event-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.