Hooks > Logs

Make stores a log of every webhook execution. Make stores webhook logs for 3 days. The webhook logs for organizations with the Enterprise plan are stored for 30 days. Read more about webhook logs.

The following endpoints allow you to retrieve webhook logs.

PreviousHooks > Incomings NextKeys

Get webhook logs

get

Retrieves a list of the specified webhook execution logs. Use the to and from parameters to filter the returned logs. The response contains:

statusId: the status of the webhook execution; 1 means successful execution, 3 means failed execution
loggedAt: the moment when Make created the log
id: the ID of the webhook execution log

Authorizations

Path parameters

hookIdintegerrequired

The ID of the webhook. Use the GET /hooks API call to get the ID values of your webhooks.

Example: 654

Query parameters

tointegeroptional

Limits data in the response to entries older than the specified timestamp. Use the UNIX timestamp format in milliseconds.

Example: 1663495749015

fromintegeroptional

Limits data in the response to entries newer than the specified timestamp. Use the UNIX timestamp format in milliseconds.

Example: 1663495749015

pg[sortBy]stringoptional

The value that will be used to sort returned entities by.

pg[offset]integeroptional

The value of entities you want to skip before getting entities you need.

pg[sortDir]string · enumoptional

The sorting order. It accepts the ascending and descending direction specifiers.

Available options:

pg[limit]integeroptional

Sets the maximum number of results per page in the API call response. For example, pg[limit]=100. The default number varies with different API endpoints.

Responses

application/json

cURL

JavaScript

Python

HTTP

curl -L \
  --url 'https://eu1.make.com/api/v2/hooks/{hookId}/logs' \
  --header 'Authorization: YOUR_API_KEY'

200

{
  "hookLogs": [
    {
      "statusId": 1,
      "parser": "gateway-webhook",
      "replayable": true,
      "sizes": {
        "before": 169,
        "after": 169
      },
      "loggedAt": "2022-09-01T13:37:19.344Z",
      "udids": [
        "1oknbf9q7ctpjwrych332ump3ny4d66s"
      ],
      "typeId": 3,
      "id": "89ea4412db0119b205daf41c84eb2160",
      "appParser": null,
      "imtId": "1662039439344_N1ZF-YIBperJkDkkOJFc"
    },
    {
      "statusId": 3,
      "parser": "gateway-webhook",
      "replayable": true,
      "sizes": {
        "before": 589,
        "after": 589
      },
      "loggedAt": "2022-09-01T13:36:19.344Z",
      "udids": [
        "1oknbf9q7ctpjwrych332ump3ny4d66s"
      ],
      "typeId": 3,
      "id": "89ea4412db0119b205daf41c84eb1020",
      "appParser": null,
      "imtId": "2662039439344_N1ZF-YIBperJkDkkOkUv"
    }
  ],
  "pg": {
    "sortBy": "loggedAt",
    "limit": 25,
    "sortDir": "desc",
    "offset": 0
  }
}

Successful response

Get webhook execution detail

get

Retrieves the specified webhook execution log. The response contains:

statusId: the status of the webhook execution; 1 means successful execution, 3 means failed execution
loggedAt: the moment when Make created the log
id: the ID of the webhook execution log
data: information about the request, header, and payload sent to the webhook.

Some webhooks don't return the data object due to their implementation. Most common examples include instant triggers for Slack, Zoom, Intercom and Facebook lead ads apps.