---
title: "Get an Audit Event"
method: GET
path: "/v2.0/auditevents/{auditEventId}"
tags: ["Audit Events"]
---

# Get an Audit Event

`GET /v2.0/auditevents/{auditEventId}`

Gets an audit event by its ID.

## Path parameters

- `auditEventId` string, required

## Headers

- `Accept` 'application/json' | 'application/hal+json' | 'application/xml' | 'text/xml' | 'text/csv'

## Response `200`

Returns audit event object

- object
  - `id` string
  - `timestamp` string — The timestamp when the action happened
  - `type` 'action' | 'create' | 'replace' | 'patch' | 'delete' | 'authentication' | 'authorization' — The type of operation that was performed
  - `user` string — The email of the user who performed the operation
  - `modifiedResources` object[] — An list of resources in the chain of the modification
    - `resourceId` string — The id of the resource in the modification chain
    - `resourceType` 'aiAgent' | 'agentassistconfig' | 'agentSettings' | 'chart' | 'connection' | 'connectionSchema' | 'endpoint' | 'extension' | 'file' | 'flow' | 'flowSettings' | 'flowState' | 'function' | 'handoverProvider' | 'intent' | 'intentDefaultReply' | 'intentLearningSentence' | 'intentRelation' | 'intentSentence' | 'intentTrainGroup' | 'knowledgeStore' | 'largeLanguageModel' | 'lexicon' | 'lexiconEntry' | 'lexiconKeyphrase' | 'lexiconSlot' | 'locale' | 'goal' | 'nluconnector' | 'nodeData' | 'nodeDescriptorSet' | 'package' | 'playbook' | 'slotFiller' | 'snapshot' | 'snippet' | 'simulation' | 'aicopilotconfig' | 'apiKey' | 'analytics' | 'connectionField' | 'conversation' | 'examplesentence' | 'functionInstance' | 'keyphrase' | 'learningsentence' | 'node' | 'playbookStep' | 'playbookStepAssert' | 'profile' | 'profileSchema' | 'project' | 'projectsettings' | 'synonym' | 'tag' | 'task' | 'trainerRecord' | 'user' | 'yesNoIntent' — Additional resource types for audit purposes
  - `payload` object — The raw payload of the operation in case it was tracked

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `402` — Upgrade your Plan to increase your Quota.
- `403` — The server understood the request but refuses to authorize it.
- `404` — The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
- `405` — The method received in the request-line is known by the origin server but not supported by the target resource.
- `409` — The request conflicts with current state of the server.
- `413` — The request entity is larger than limits defined by server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `501` — The server does not support the functionality required to fulfill the request.
- `502` — The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- `503` — The server is not ready to handle the request.
- `504` — The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

---

[API](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/versions/85b2872bdfb7/schema)