Audit logs
The following endpoints allow you to get the organization and team audit logs and their details.
You can read more about audit logs in our Help Center.
Gets a list of all audit log entries for the specified organization.
The audit log entries in the response are sorted by the triggeredAt property in descending order by default. You can use pagination to navigate through a large number of entries.
You can get the audit log entries only for organizations in which you have the "Admin" or "Owner" roles. Otherwise, you get the 403 error.
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.
GET /api/v2/audit-logs/organization/{organizationId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Audit log entries for the specified organization.
{
"auditLogs": {
"uuid": "c37c7292-35cd-4dc4-9113-21b23beaea7d",
"createdAt": "2024-05-24T14:22:16.879Z",
"triggeredAt": "2024-04-19T12:05:22Z",
"organizationId": 3,
"organization": {
"id": 3,
"name": "John Doe's Organization"
},
"eventName": "webhook_created",
"team": {
"id": 212,
"name": "John Doe's Team"
},
"actor": {
"id": 212,
"name": "John Doe",
"email": "[email protected]"
},
"targetId": "3000",
"version": {
"from": "1.0.0",
"to": "1.0.1"
}
},
"pg": {
"sortBy": "triggeredAt",
"sortDir": "desc",
"offset": 0,
"limit": 100,
"totalCount": 60
}
}Gets available audit logs filters for the organization.
You can use the data in the response to filter audit log entries you get from the GET /audit-logs/organization/{organizationId} endpoint.
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
GET /api/v2/audit-logs/organization/{organizationId}/filters HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Successfully retrieve of available audit logs filters for the organization
{
"teams": [
{
"id": 1,
"name": "John Doe's Team"
}
],
"users": [
{
"id": 1,
"name": "John Doe",
"email": "[email protected]"
}
],
"events": [
{
"header": "Webhooks",
"items": [
{
"label": "Webhook created",
"value": "webhook_created"
},
{
"label": "Webhook updated",
"value": "webhook_updated"
}
]
}
]
}Gets a list of all audit log entries for the specified team.
The audit log entries in the response are sorted by the triggeredAt property in descending order by default. You can use pagination to navigate through a large number of entries.
You can get the audit log entries only for teams in which you have the "Team Admin" role. Otherwise, you get the 403 error.
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.
GET /api/v2/audit-logs/team/{teamId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Audit log entries for the specified team.
{
"auditLogs": {
"uuid": "c37c7292-35cd-4dc4-9113-21b23beaea7d",
"createdAt": "2024-05-24T14:22:16.879Z",
"triggeredAt": "2024-04-19T12:05:22Z",
"organizationId": 3,
"organization": {
"id": 3,
"name": "John Doe's Organization"
},
"eventName": "webhook_created",
"team": {
"id": 212,
"name": "John Doe's Team"
},
"actor": {
"id": 212,
"name": "John Doe",
"email": "[email protected]"
},
"targetId": "3000",
"version": {
"from": "1.0.0",
"to": "1.0.1"
}
},
"pg": {
"sortBy": "triggeredAt",
"sortDir": "desc",
"offset": 0,
"limit": 100,
"totalCount": 60
}
}Gets available audit logs filters for the team.
You can use the data in the response to filter audit log entries you get from the GET /audit-logs/team/{teamId} endpoint.
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
GET /api/v2/audit-logs/team/{teamId}/filters HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Successfully retried available audit logs filters for the team
{
"users": [
{
"id": 1,
"name": "John Doe",
"email": "[email protected]"
}
],
"events": [
{
"header": "Webhooks",
"items": [
{
"label": "Webhook created",
"value": "webhook_created"
},
{
"label": "Webhook updated",
"value": "webhook_updated"
}
]
}
]
}Gets details of the audit log entry with the specified UUID.
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
GET /api/v2/audit-logs/{organizationId}/{uuid} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Successful response
{
"details": {
"webhookName": "Webhook from John Doe",
"webhookType": "http"
},
"uuid": "c37c7292-35cd-4dc4-9113-21b23beaea7d",
"createdAt": "2024-05-24T14:22:16.879Z",
"triggeredAt": "2024-04-19T12:05:22Z",
"organizationId": 3,
"organization": {
"id": 3,
"name": "John Doe's Organization"
},
"eventName": "webhook_created",
"team": {
"id": 212,
"name": "John Doe's Team"
},
"actor": {
"id": 212,
"name": "John Doe",
"email": "[email protected]"
},
"targetId": "3000",
"version": {
"from": "1.0.0",
"to": "1.0.1"
}
}Last updated