Any of the following permissions is required:
manage-incoming-integrationsmanage-own-incoming-integrationsmanage-outgoing-integrationsmanage-own-outgoing-integrations
The endpoint returns the integration history based on the user permissions.
Changelog
| Version | Description |
|---|---|
| 1.1.0 | Separate permissions in incoming and outgoing. |
| 0.53.0 | Added |
The authorization token of the user.
The user ID of the user.
The integration ID.
Number of items to "skip" in the query, i.e. requests return count items, skipping the first offset items. Refer to the official documentation to learn more.
List of fields to order by, and in which direction. This is a JSON object, with properties listed in desired order, with values of 1 for ascending, or -1 for descending. For example, {"value": -1, "_id": 1}. Refer to the official documentation to learn more.
This parameter allows you to use MongoDB query operators to search for specific data. For example, to query users with a name that contains the letter "g": query={ "name": { "$regex": "g" } }. Refer to the official documentation to learn more.
This parameter accepts a JSON object with properties that have a value of 1 or 0 to include or exclude them in the response. For example, to only retrieve the usernames of users: fields={ "username": 1 }. Refer to the official documentation to learn more.
{
"history": [],
"offset": 0,
"items": 0,
"total": 0,
"success": true
}Bad Request
{
"success": false,
"error": "must have required property 'id' [invalid-params]",
"errorType": "invalid-params"
}Unauthorized
{
"status": "error",
"message": "You must be logged in to do this."
}