Scenarios > Logs

The following endpoints allow you to manage scenarios logs.

List scenario logs

get

https://eu1.make.com/api/v2https://eu2.make.com/api/v2https://us1.make.com/api/v2https://us2.make.com/api/v2https://eu1.make.celonis.com/api/v2https://us1.make.celonis.com/api/v2

/scenarios/{scenarioId}/logs

Retrieves a collection of all logs for a scenario with a given ID. Returned logs are sorted by imtId in descending order.

Required scopes

This endpoint requires the following scopes:

Authorizations

token

AuthorizationstringRequired

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.

Path parameters

scenarioIdintegerRequired

The ID of the scenario. You can get the scenarioId with the List scenarios API call.

Example: 112

Query parameters

fromintegerOptional

The timestamp in milliseconds that defines the starting point of time from which the logs should be retrieved. Older logs will not be returned.

Example: 1632395547

tointegerOptional

The timestamp in milliseconds that defines the ending point of time to which the logs should be retrieved. Newer logs will not be returned.

Example: 1632395548

statusinteger · enumOptional

Filters logs by the execution status. 1 is for success, 2 is for warning, and 3 is for error.

Example: 2Possible values:

showCheckRunsbooleanOptional

If set to true, this parameter specifies that check runs should be hidden in the returned results. Check runs concern scenarios starting with a trigger in cases when the trigger does not find anything new.

Example: true

pg[offset]integerOptional

The number of entities you want to skip before getting entities you want.

pg[limit]integerOptional

The maximum number of entities you want to get in the response.

pg[showLast]booleanOptional

Include records with last value in the result set. Just in case of the last based paging.

Example: true

pg[last]integerOptional

The last retrieved key. In response, you get only entries that follow after the key.

Example: 10

pg[sortBy]stringOptional

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

pg[sortDir]string · enumOptional

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

Possible values:

Responses

200

Successful response

application/json

get

/scenarios/{scenarioId}/logs

HTTPcURLJavaScriptPython

GET /api/v2/scenarios/{scenarioId}/logs HTTP/1.1
Host: eu1.make.com
Authorization: Token your-api-token
Accept: */*

200

Successful response

{
  "scenarioLogs": [
    {
      "imtId": "1632371744497_scenario.1229.auto.da518adcd14b4b64ac6358823ccb80ca",
      "duration": 19979,
      "operations": 10,
      "transfer": 3942,
      "centicredits": 1000,
      "organizationId": 21,
      "teamId": 27,
      "id": "da518adcd14b4b64ac6358823ccb80ca",
      "type": "auto",
      "authorId": null,
      "instant": false,
      "timestamp": "2021-09-23T04:35:44.497Z",
      "status": 1
    }
  ],
  "pg": {
    "sortBy": "imtId",
    "sortDir": "desc",
    "last": "1632371803593_scenario.1229.auto.3cf2f332f74f43f1b2c4ae431cbedb5b",
    "showLast": false,
    "limit": 50
  }
}

Get execution log

get

https://eu1.make.com/api/v2https://eu2.make.com/api/v2https://us1.make.com/api/v2https://us2.make.com/api/v2https://eu1.make.celonis.com/api/v2https://us1.make.celonis.com/api/v2

/scenarios/{scenarioId}/logs/{executionId}

Retrieves an execution log with a given ID for a scenario with a given ID. It returns the execution details such as execution duration, type, and status.

Required scopes

This endpoint requires the following scopes:

Authorizations

token

AuthorizationstringRequired

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.

Path parameters

scenarioIdintegerRequired

The ID of the scenario. You can get the scenarioId with the List scenarios API call.

Example: 112

executionIdstringRequired

The unique ID of the scenario execution. It can be retrieved from the List scenario logs endpoint under the ID key.

Example: cc1c49323b344687a324888762206003

Responses

200

Execution log retrieved

application/json

get

/scenarios/{scenarioId}/logs/{executionId}

HTTPcURLJavaScriptPython

GET /api/v2/scenarios/{scenarioId}/logs/{executionId} HTTP/1.1
Host: eu1.make.com
Authorization: Token your-api-token
Accept: */*

200

Execution log retrieved

{
  "scenarioLogs": {
    "imtId": "1632398122946_scenario.5.manual.cc1c49323b344687a324888762206003",
    "duration": 5611,
    "operations": 2,
    "transfer": 5,
    "centicredits": 200,
    "organizationId": 5,
    "teamId": 16,
    "id": "cc1c49323b344687a324888762206003",
    "type": "manual",
    "authorId": 5,
    "instant": true,
    "timestamp": "2021-09-23T11:55:22.946Z",
    "status": 1
  }
}

Get scenario execution details

get

https://eu1.make.com/api/v2https://eu2.make.com/api/v2https://us1.make.com/api/v2https://us2.make.com/api/v2https://eu1.make.celonis.com/api/v2https://us1.make.celonis.com/api/v2

/scenarios/{scenarioId}/executions/{executionId}

Retrieves details about an execution.

Required scopes

This endpoint requires the following scopes:

Authorizations

token

AuthorizationstringRequired

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.

Path parameters

scenarioIdintegerRequired

The ID of the scenario. You can get the scenarioId with the List scenarios API call.

Example: 112

executionIdstringRequired

The unique ID of the scenario execution. It can be retrieved from the List scenario logs endpoint under the ID key.

Example: cc1c49323b344687a324888762206003

Responses

200

Successful response

application/json

get

/scenarios/{scenarioId}/executions/{executionId}

HTTPcURLJavaScriptPython

GET /api/v2/scenarios/{scenarioId}/executions/{executionId} HTTP/1.1
Host: eu1.make.com
Authorization: Token your-api-token
Accept: */*

200

Successful response

{
  "status": "SUCCESS",
  "outputs": {
    "output1": "text output",
    "output2": 123
  }
}

Deprecated

Operations by Module

get

https://eu1.make.com/api/v2https://eu2.make.com/api/v2https://us1.make.com/api/v2https://us2.make.com/api/v2https://eu1.make.celonis.com/api/v2https://us1.make.celonis.com/api/v2

/scenarios/{scenarioId}/modules/operations

Retrieves an aggregated list of operations per module within a specified time period.

Required scopes

This endpoint requires the following scopes:

Authorizations

token

AuthorizationstringRequired

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.

Path parameters

scenarioIdintegerRequired

The ID of the scenario. You can get the scenarioId with the List scenarios API call.

Example: 112

Query parameters

daysintegerOptional

Days to summarize retrospectively. Default 1, must be between 1 and 30.

Example: 1

Responses

200

Module log retrieved

application/json

get

/scenarios/{scenarioId}/modules/operations

HTTPcURLJavaScriptPython

GET /api/v2/scenarios/{scenarioId}/modules/operations HTTP/1.1
Host: eu1.make.com
Authorization: Token your-api-token
Accept: */*

200

Module log retrieved

{
  "operations": [
    {
      "moduleId": 1,
      "total": 315,
      "warnings": 0,
      "errors": 1
    }
  ]
}

List module logs

get

https://eu1.make.com/api/v2https://eu2.make.com/api/v2https://us1.make.com/api/v2https://us2.make.com/api/v2https://eu1.make.celonis.com/api/v2https://us1.make.celonis.com/api/v2

/scenarios/{scenarioId}/modules/{moduleId}/logs

Retrieves an operation logs of a given module within a given scenario. Returns the operation details such as execution id, timestamp or status.

Required scopes

This endpoint requires the following scopes:

Authorizations

token

AuthorizationstringRequired

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.

Path parameters

scenarioIdintegerRequired

The ID of the scenario. You can get the scenarioId with the List scenarios API call.

Example: 112

moduleIdintegerRequired

The unique ID of the scenario module. It is available in the scenario blueprint that can be retrieved from the Get scenario blueprint endpoint.

Example: 1

Query parameters

pg[offset]integerOptional

The number of entities you want to skip before getting entities you want.

pg[limit]integerOptional

The maximum number of entities you want to get in the response.

pg[showLast]booleanOptional

Include records with last value in the result set. Just in case of the last based paging.

Example: true

pg[last]integerOptional

The last retrieved key. In response, you get only entries that follow after the key.

Example: 10

pg[sortBy]stringOptional

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

pg[sortDir]string · enumOptional

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

Possible values:

Responses

200

Module logs retrieved

application/json

get

/scenarios/{scenarioId}/modules/{moduleId}/logs

HTTPcURLJavaScriptPython

GET /api/v2/scenarios/{scenarioId}/modules/{moduleId}/logs HTTP/1.1
Host: eu1.make.com
Authorization: Token your-api-token
Accept: */*

200

Module logs retrieved

{
  "moduleLogs": [
    {
      "imtId": "1632398122946_scenario.5.manual.cc1c49323b344687a324888762206003",
      "executionId": "384ef653d04844589e1c8427c13ffb15",
      "organizationId": 5,
      "teamId": 16,
      "scenarioId": 5,
      "timestamp": "2021-09-23T11:55:22.946Z",
      "status": 1,
      "bundles": 1
    }
  ]
}