Retrieve content change logs of board items
GET/v2/orgs/:org_id/content-logs/items
Retrieves content changes for board items within your organization. Content changes are actions that users can perform on board items, such as updating a sticky note's text. You can retrieve results for a specific time period. You can also filter results based on the board IDs and the emails of users who created, modified, or deleted a board item. Additionally, results can be paginated for easier viewing and processing.
Required scope
contentlogs:exportRate limiting
Level 4Enterprise only
This API is available only for Enterprise plan users. You can only use this endpoint if you have the role of a Company Admin.
Request
Path Parameters
Unique identifier of the organization.
Query Parameters
Possible values: <= 15
List of board IDs for which you want to retrieve the content logs.
Possible values: <= 15
Filter content logs based on the list of emails of users who created, modified, or deleted the board item.
Filter content logs based on the date and time when the board item was last modified. This is the start date and time for the modified date duration. Format: UTC, adheres to ISO 8601, includes a trailing Z offset.
Filter content logs based on the date and time when the board item was last modified. This is the end date and time for the modified date duration. Format: UTC, adheres to ISO 8601, includes 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 portion of the collection, set the cursor parameter equal to the cursor value you received in the response of the previous request.
Possible values: >= 1
and <= 1000
Default value: 1000
The maximum number of results to return per call. If the number of logs in the response is greater than the limit specified, the response returns the cursor parameter with a value.
Possible values: [asc
, desc
]
Default value: asc
Sort order in which you want to view the result set based on the modified date. To sort by an ascending modified date, specify asc
. To sort by a descending modified date, specify desc
.
Responses
- 200
- 400
- 401
- 403
- 404
- 429
Response from the API that includes content logs of board items such as data, size of the data list, pagination cursor, and pagination limit.
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
The maximum number of results to return per call. If the number of logs in the response is greater than the limit specified, the response returns the cursor parameter with a value.
Number of results returned in the response considering the cursor and the limit values sent in the request. For example, if there are 20 results, the request does not have a cursor value, and the limit set to 10, the size of the results will be 10. In this example, the response will also return a cursor value that can be used to retrieve the next set of 10 remaining results in the collection.
data
object[]
Contains the list of content logs for a board item.
Unique identifier of the content log.
Unique identifier of the board item.
Type of the board item.
User action in the form of insert, update, or delete.
Unique identification of the board to which the item belongs.
Indicates if the board is a hidden board. Returns true
if board item is hidden.
Date and time when the board item was created.
Format: UTC, adheres to ISO 8601, includes a trailing Z offset.
createdBy
object
Contains user information.
Unique identifier of the user.
Email of the user.
First name of the user.
Last name of the user.
Date and time when the board item was last modified.
Format: UTC, adheres to ISO 8601, includes a trailing Z offset.
modifiedBy
object
Contains user information.
Unique identifier of the user.
Email of the user.
First name of the user.
Last name of the user.
logData
object
Content log object representing the current state of the board item at the modifiedAt
time.
Text extracted from the board item.
metadata
object
Metadata representing more information that might be relevant for a specific board item.
Indicator of the position of the next page of the result. To retrieve the next page, make another query setting its cursor field to the value returned by the current query. If the value is empty, there are no more pages to fetch.
Default value: cursor-list
Type of the object returned.
{
"limit": 20,
"size": 1,
"data": [
{
"id": 1,
"itemId": "3458764549483493025",
"type": "sticker",
"action": "update",
"boardKey": "o9J_kzlUDmo=",
"hidden": true,
"createdAt": "2023-06-24T17:32:28Z",
"createdBy": {
"id": "3458764517517852417",
"email": "john.smith.demo@miro.com",
"firstName": "John",
"lastName": "Smith"
},
"modifiedAt": "2023-06-24T17:32:28Z",
"modifiedBy": {
"id": "3458764517517852417",
"email": "john.smith.demo@miro.com",
"firstName": "John",
"lastName": "Smith"
},
"logData": {
"text": "<p>data sample</p>",
"metadata": {}
}
}
],
"cursor": "MTY2OTg4NTIwMDAwMHwxMjM=",
"type": "cursor-list"
}
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"
}
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"
}