Audit logs
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
The ID of the organization.
11The identification of the teams for which you want to get the audit log entries. You can use either team IDs or team names.
The team name can contain any valid UTF8 symbols and spaces.
team 11["team 1","team 2"][1,2,3]Use the dateFrom parameter to get audit log entries from the specified date or newer. Specify the date in the YYYY-MM-DD format.
2021-09-23T00:00:00.000ZUse the dateTo parameter to get audit log entries until the specified date or older. Specify the date in the YYYY-MM-DD format.
2021-09-24T00:00:00.000ZThe list of events for which you want to get audit log entries. To specify multiple events, use the array notation like: GET /audit-logs/organization/{organizationId}?event[0]=key_created&event[1]=connection_created.
You can check the list of supported events with the API call GET /audit-logs/organization/{organizationId}/filters in the events array in the response.
{"value":["key_created","connection_created"]}webhook_disabled["webhook_disabled","webhook_updated","webhook_deleted"]The identification of the users for whose actions you want to get the audit log entries. You can use either user IDs or user names.
The user name can contain any valid UTF8 symbols and spaces.
author 11["author 1","author 2"][1,2,3]The number of entities you want to skip before getting entities you want.
The maximum number of entities you want to get in the response.
The last retrieved key. In response, you get only entries that follow after the key.
10Specify the response property values that Make will use to sort the audit log entries in the response. The default is triggeredAt.
The sorting order. It accepts the ascending and descending direction specifiers.
Set to true to get also the total number of audit log entries in the response.
trueAudit log entries for the specified organization.
Audit log entries for the specified organization.
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
The ID of the organization.
11Successfully retrieve of available audit logs filters for the organization
Successfully retrieve of available audit logs filters for the organization
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
The ID of the team.
11Use the dateFrom parameter to get audit log entries from the specified date or newer. Specify the date in the YYYY-MM-DD format.
2021-09-23T00:00:00.000ZUse the dateTo parameter to get audit log entries until the specified date or older. Specify the date in the YYYY-MM-DD format.
2021-09-24T00:00:00.000ZThe list of events for which you want to get audit log entries. To specify multiple events, use the array notation like: GET /audit-logs/team/{teamId}?event[0]=key_created&event[1]=connection_created.
You can check the list of supported events with the API call GET /audit-logs/team/{teamId}/filters in the events array in the response.
{"value":["key_created","connection_created"]}webhook_disabled["webhook_disabled","webhook_updated","webhook_deleted"]The identification of the users for whose actions you want to get the audit log entries. You can use either user IDs or user names.
The user name can contain any valid UTF8 symbols and spaces.
author 11["author 1","author 2"][1,2,3]The number of entities you want to skip before getting entities you want.
The maximum number of entities you want to get in the response.
The last retrieved key. In response, you get only entries that follow after the key.
10Specify the response property values that Make will use to sort the audit log entries in the response. The default is triggeredAt.
The sorting order. It accepts the ascending and descending direction specifiers.
Set to true to get also the total number of audit log entries in the response.
trueAudit log entries for the specified team.
Audit log entries for the specified team.
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
The ID of the team.
11Successfully retried available audit logs filters for the team
Successfully retried available audit logs filters for the team
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
The UUID of the audit log entry.
c37c7292-35cd-4dc4-9113-21b23beaea7dSuccessful response
Successful response
Last updated

