Skip to main content
GET
/
v2.0
/
auditevents
/
{auditEventId}
Get an Audit Event
curl --request GET \
  --url https://api-trial.cognigy.ai/new/v2.0/auditevents/{auditEventId} \
  --header 'X-API-Key: <api-key>'
{
  "id": "<string>",
  "timestamp": "2020-04-27T14:22:11.000Z",
  "type": "create",
  "user": "hans.mustermann@xyz.com",
  "modifiedResources": [
    {
      "resourceId": "5e997f0cdcfc57730cf32941",
      "resourceType": "node"
    }
  ],
  "payload": {
    "name": "new resource name"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.cognigy.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

ā€‹
X-API-Key
string
header
required

Supply the API Key in the HTTP-Header

Headers

ā€‹
Accept
enum<string>

The Accept header specifies the media type that the client expects in the response. Available options: application/json, application/hal+json, application/xml, text/xml, text/csv. The default value is application/json.

Available options:
application/json,
application/hal+json,
application/xml,
text/xml,
text/csv

Path Parameters

ā€‹
auditEventId
string
required

Audit event ID

Response

Returns audit event object

ā€‹
id
string
Required string length: 24
Pattern: ^[a-z0-9]{24}$
ā€‹
timestamp
string

The timestamp when the action happened

Example:

"2020-04-27T14:22:11.000Z"

ā€‹
type
enum<string>

The type of operation that was performed

Available options:
action,
create,
replace,
patch,
delete,
authentication,
authorization
Example:

"create"

ā€‹
user
string

The email of the user who performed the operation

Example:

"hans.mustermann@xyz.com"

ā€‹
modifiedResources
object[]

An list of resources in the chain of the modification

ā€‹
payload
object

The raw payload of the operation in case it was tracked

Example:
{ "name": "new resource name" }