Get audit logs
GET/v2/audit/logs
Retrieves a page of audit events.
Required scope
auditlogs:readRate limiting
Level 2Request
Query Parameters
Retrieve audit logs created after the date and time provided. This is the start date of the duration for which you want to retrieve audit logs. For example, if you want to retrieve audit logs between 2023-03-30T17:26:50.000Z
and 2023-04-30T17:26:50.000Z
, provide 2023-03-30T17:26:50.000Z
as the value for the createdAfter
parameter.
Format: UTC, adheres to ISO 8601, including milliseconds and a trailing Z offset."
Retrieve audit logs created before the date and time provided. This is the end date of the duration for which you want to retrieve audit logs. For example, if you want to retrieve audit logs between 2023-03-30T17:26:50.000Z
and 2023-04-30T17:26:50.000Z
, provide 2023-04-30T17:26:50.000Z
as the value for the createdBefore
parameter.
Format: UTC, adheres to ISO 8601, including milliseconds and a trailing Z offset.
A cursor-paginated method returns a portion of the total set of results based on the limit
specified and a cursor
that points to the next portion of the results. To retrieve the next set of results of the collection, set the cursor
parameter in your next request to the appropriate cursor value returned in the response.
Maximum number of results returned based on the limit
specified in the request. For example, if there are 30
results, the request has no cursor
value, and the limit
is set to 20
,the size
of the results will be 20
. The rest of the results will not be returned. To retrieve the rest of the results, you must make another request and set the appropriate value for the cursor
parameter value that you obtained from the response.
Default: 100
Possible values: [ASC
, DESC
]
Sort order in which you want to view the result set. Based on the value you provide, the results are sorted in an ascending or descending order of the audit log creation date (audit log createdAt
parameter).
Default: ASC
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 429
Audit logs fetched
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Type of the response, in this case it's always 'cursor-list'
Page limit
Item count in current page
The key that should be used as the cursor request parameter to fetch the next page
content
object[]
Audit events list
Audit event id
context
object
Audit context
Ip address associated with the audit context
team
object
Team associated with the audit context
Id of the team
Name of the team
organization
object
Organization associated with the audit context
Id of the organization
Name of the organization
object
object
The object related with the audit event
Id of the object
Name of the object
Time when the audit event has been created
Details json related to the audit event
createdBy
object
The details regarding the creator of the audit event
Possible values: [user
, application
, scim_provisioner
, miro_automation
]
Type of the creator
Id of the creator
Name of the creator
Email of the creator
Event type of the audit event
{
"type": "cursor-list",
"limit": 10,
"size": 2,
"cursor": "2023-09-01T09:30:10.840687Z#1234567890123456789-DDB",
"content": [
{
"id": "2023-09-01T09:30:10.840687Z#1234567890123456789-DDB",
"context": {
"ip": "0.0.0.0",
"team": {
"id": "1234567890123456789",
"name": "Example Team"
},
"organization": {
"id": "1234567890123456789",
"name": "Example Organization"
}
},
"object": {
"id": "1234567890123456789",
"name": "Example Object"
},
"createdAt": "2023-09-01T09:30:10.840+0000",
"details": "{ \"authType\": \"SSO\", \"mfaFactorType\": \"NONE\" }",
"createdBy": {
"type": "user",
"id": "1234567890123456789",
"name": "John Smith",
"email": "john.smith@miro.com"
},
"event": "sign_in_succeeded"
}
]
}
Malformed request
- application/json
- Schema
- Example (from schema)
Schema
Default value: 400
HTTP status code.
Default value: invalidParameters
Description of the status code.
Explanation for the error
Default value: error
Type of the object returned.
{
"status": 400,
"code": "invalidParameters",
"message": "string",
"type": "error"
}
Invalid authentication credentials
- application/json
- Schema
- Example (from schema)
Schema
Default value: 401
HTTP status code.
Default value: tokenNotProvided
Description of the status code.
Explanation for the error
Default value: error
Type of the object returned.
{
"status": 401,
"code": "tokenNotProvided",
"message": "string",
"type": "error"
}
Invalid access
- application/json
- Schema
- Example (from schema)
Schema
Default value: 403
HTTP status code.
Default value: forbiddenAccess
Description of the status code.
Explanation for the error
Default value: error
Type of the object returned.
{
"status": 403,
"code": "forbiddenAccess",
"message": "string",
"type": "error"
}
Invalid access
- application/json
- Schema
- Example (from schema)
Schema
Default value: 404
HTTP status code.
Default value: notFound
Description of the status code.
Explanation for the error
Default value: error
Type of the object returned.
{
"status": 404,
"code": "notFound",
"message": "string",
"type": "error"
}
Conflict
- application/json
- Schema
- Example (from schema)
Schema
Default value: 409
HTTP status code.
Default value: conflict
Description of the status code.
Explanation for the error
Default value: error
Type of the object returned.
{
"status": 409,
"code": "conflict",
"message": "string",
"type": "error"
}
Too many requests
- application/json
- Schema
- Example (from schema)
Schema
Default value: 429
HTTP status code.
Default value: tooManyRequests
Description of the status code.
Explanation for the error
Default value: error
Type of the object returned.
{
"status": 429,
"code": "tooManyRequests",
"message": "string",
"type": "error"
}