Get support

Teams

Teams are containers that contain scenarios and data accessible only by the members of the team. The API endpoints discussed further allow you to manage teams. Read more about teams.

List teams

get

Gets the list of teams in the organization with specified organizationId.

Authorizations
Query parameters
organizationIdintegerRequired

The ID of the organization.

Example: 1
colsstring[]Optional

Specifies columns that are returned in the response. Use the cols[] parameter for every column that you want to return in the response. For example GET /endpoint?cols[]=key1&cols[]=key2 to get both key1 and key2 columns in the response.

Check the "Filtering" section for a full example.

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.

Possible values:
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
200
Successful response
application/json
get
GET /api/v2/teams HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "default-cols": {
    "summary": "Gets the list of teams",
    "description": "Gets the list of teams in the organization with specified `organizationId`",
    "teams": [
      {
        "id": 5,
        "name": "My Team",
        "organizationId": 5
      }
    ],
    "pg": {
      "sortBy": "name",
      "sortDir": "asc",
      "limit": 10000,
      "offset": 0
    }
  },
  "all-cols": {
    "summary": "Gets the list of teams with all the data",
    "description": "Gets the list of teams with all the data in the organization with specified `organizationId`",
    "teams": [
      {
        "id": 5,
        "name": "My Team",
        "organizationId": 5,
        "operations": "2015",
        "transfer": "27914902",
        "operationsLimit": 10000,
        "transferLimit": "100",
        "consumedOperations": 10,
        "consumedTransfer": "100",
        "isPaused": false
      }
    ],
    "pg": {
      "sortBy": "name",
      "sortDir": "asc",
      "limit": 10000,
      "offset": 0
    }
  }
}

Create a team

post

Create a new team in the organization with the specified organizationId.

Authorizations
Body
namestringRequired

The name of the team.

organizationIdintegerRequired

The ID of the organization.

operationsLimitintegerOptional

The maximum number of operations allowed for the team.

Responses
200
Successful response
application/json
post
POST /api/v2/teams HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 38

{
  "name": "New Team",
  "organizationId": 1
}
200

Successful response

{
  "team": {
    "id": 26,
    "name": "New Team",
    "organizationId": 1,
    "operationsLimit": 1,
    "transferLimit": "536870"
  },
  "userTeamRole": {
    "usersRoleId": 1,
    "userId": 1,
    "teamId": 26,
    "changeable": false
  }
}

Get team details

get

Returns information about the team with the specified teamId.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
Query parameters
colsstring[]Optional

Specifies columns that are returned in the response. Use the cols[] parameter for every column that you want to return in the response. For example GET /endpoint?cols[]=key1&cols[]=key2 to get both key1 and key2 columns in the response.

Check the "Filtering" section for a full example.

Example: {"value":["id","name","organizationId","activeScenarios","activeApps","operations","transfer","operationsLimit","transferLimit","consumedOperations","consumedTransfer","isPaused"]}
Responses
200
Successful response
application/json
get
GET /api/v2/teams/{teamId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "team": {
    "id": 1,
    "name": "Team 1",
    "organizationId": 1,
    "scenarioDrafts": false
  }
}

Delete a team

delete

Deletes the team with the specified teamId. Make also deletes all data associated with the team, for example scenarios, webhooks or custom team variables.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
Query parameters
confirmedbooleanOptional

Set this parameter to true to confirm the team deletion. Otherwise, the API call returns an error and the team is not deleted.

Example: true
Responses
200
Successful response
application/json
delete
DELETE /api/v2/teams/{teamId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "team": 22
}

List team variables

get

Retrieves the collection of team variables. The response contains all team variables if your account has the custom variables feature available. Otherwise, the response contains only Make system variables.

Check availability of the custom variables feature with the API call GET /organizations/{organizationId} for the organization to which the team belongs. If the response contains "customVariables": true pair in the license object then you have access to the custom variables feature.

Refer to the Make pricing page for Make pricing plans overview.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
Responses
200
Successful response
application/json
get
GET /api/v2/teams/{teamId}/variables HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "teamVariables": {
    "name": "userId",
    "typeId": 1,
    "value": 123,
    "isSystem": false
  }
}

Create team variable

post

Creates new team variable. You can check the availability of the custom variables feature with the API call GET /organizations/{organizationId} for the organization to which the team belongs. If the API call response contains "customVariables": true pair in the license object then you have access to the custom variables feature.

A successful response contains all information about the new variable. If you don't have the custom variables feature available then the API call returns the error 404.

Refer to the Make pricing page for Make pricing plans overview.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
Body
typeIdnumberOptional

Number representing the type of the custom variable. The mapping of typeId and variable types is as follows:

  • 1: number,
  • 2: string,
  • 3: boolean,
  • 4: datein ISO 8601 compliant format YYYY-MM-DDTHH:mm:ss.sssZ. For example: 1998-03-06T12:31:00.000Z.
valueone ofOptional

Value assigned to the custom variable.

stringOptional
or
booleanOptional
or
numberOptional
or
or
namestringOptional

The name of the variable. You can use letters, digits, $ and _ characters in the custom variable name.

Responses
200
Successful response
application/json
post
POST /api/v2/teams/{teamId}/variables HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 40

{
  "typeId": 1,
  "value": 123,
  "name": "userId"
}
200

Successful response

{
  "teamVariable": {
    "name": "userId",
    "typeId": 1,
    "value": 123,
    "isSystem": false
  }
}

Delete team variable

delete

Deletes team variable.

If you don't have the custom variables feature available then the API call returns error 404. Check the availability of the custom variables feature with the API call GET /organizations/{organizationId} for the organization in which the team belongs. If the response contains "customVariables": true pair in the license object then you have access to the custom variables feature.

Refer to the Make pricing page for Make pricing plans overview.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
variableNamestringRequired

The name of the custom variable.

Example: userID
Query parameters
confirmedbooleanOptional

Set to true to confirm deleting the custom variable. Otherwise the API call fails with the error IM004 (406).

Example: true
Responses
200
Successful response
application/json
delete
DELETE /api/v2/teams/{teamId}/variables/{variableName} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "ok": 1
}

Update team variable

patch

Updates custom team variable with the specified variable name. Only parameters specified in the request body are updated.

You can check the availability of the custom variables feature with the API call GET /organizations/{organizationId} for the organization to which the team belongs. If the response contains "customVariables": true pair in the license object then you have access to the custom variables feature.

A successful response contains all information about the updated variable. If you don't have the custom variables feature available then the API call returns the error 404.

Refer to the Make pricing page for the Make pricing plans overview.

Update the variable typeId accordingly when you are updating the variable value. Make checks whether the variable type and value match in the request body. There is no check for incorrect variable type when you update only variable value and vice versa.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
variableNamestringRequired

The name of the custom variable.

Example: userID
Body
typeIdnumberOptional

Number representing the type of the custom variable. The mapping of typeId and variable types is as follows:

  • 1: number,
  • 2: string,
  • 3: boolean,
  • 4: datein ISO 8601 compliant format YYYY-MM-DDTHH:mm:ss.sssZ. For example: 1998-03-06T12:31:00.000Z.
valueone ofOptional

Value assigned to the custom variable.

stringOptional
or
booleanOptional
or
numberOptional
or
or
Responses
200
Successful response
application/json
patch
PATCH /api/v2/teams/{teamId}/variables/{variableName} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 13

{
  "value": 221
}
200

Successful response

{
  "teamVariable": {
    "name": "userId",
    "typeId": 1,
    "value": 251
  }
}

History of custom variable updates

get

Gets the history of updates of the specified custom variable. The response contains the ID value of the variable history entry and a diffObject. The diffObject contains:

  • the original value,

  • the new value,

  • the timestamp of the update,

  • the author of the update.

If the variable doesn't have any updates, the diffObject contains the current value of the variable instead of the original and new values.

The update history entries are sorted from newest to latest.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
variableNamestringRequired

The name of the custom variable.

Example: userID
Responses
200
Successful response
application/json
get
GET /api/v2/teams/{teamId}/variables/{variableName}/history HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "teamVariableHistory": [
    {
      "id": 1,
      "diffObject": {
        "name": "userId",
        "value": 11,
        "typeId": 1
      },
      "changed": "2022-08-02T09:37:05.364Z",
      "action": "team_variable_created",
      "author": "Jon Doe"
    },
    {
      "id": 2,
      "diffObject": {
        "old": {
          "value": 11,
          "typeId": 1
        },
        "new": {
          "value": 23,
          "typeId": 1
        }
      },
      "changed": "2022-08-02T09:37:05.364Z",
      "action": "team_variable_edited",
      "author": "Jon Doe"
    }
  ]
}

Get team usage

get

Retrieves a list of daily operations and data transfer usage for all scenarios within a specified team over the past 30 days.

By default, the endpoint uses the timezone of the user making the API call to define the start and end of each day in the 30-day timeframe.

To use the organization's timezone instead, set the organizationTimezone parameter to true. This ensures that the daily aggregates align with the organization's operational hours. This is especially useful for scenarios where aggregated data needs to align with the organization's operational hours.

For instance, a remote data analyst in India working for a Czech company can set organizationTimezone=true to ensure the usage data reflects the company's timezone, providing more relevant and accurate insights for organizational reporting and analysis.

For more information on timezones in Make, please refer to our Help Center article.

Authorizations
Path parameters
teamIdintegerRequired

The ID of the team.

Example: 22
Query parameters
organizationTimezonebooleanOptional

When set to true, the endpoint will calculate and return usage data based on the organization's timezone instead of the user's local timezone.

Example: true
Responses
200
Successfully retrieved usage data
application/json
get
GET /api/v2/teams/{teamId}/usage HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successfully retrieved usage data

{
  "data": [
    {
      "date": "2024-05-30",
      "operations": 9,
      "dataTransfer": 135
    },
    {
      "date": "2024-05-31",
      "operations": 15,
      "dataTransfer": 157
    }
  ]
}

Get team LLM configuration

get

Gets the LLM configuration for the specified team.

Authorizations
Path parameters
teamIdinteger · min: 1Required

The ID of the team.

Responses
200
Successful response
application/json
get
GET /api/v2/teams/{teamId}/llm-configuration HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "aiMappingAccountId": 123,
  "aiMappingModelName": "gpt-4"
}

Update team LLM configuration

patch

Updates the LLM configuration for the specified team.

Authorizations
Path parameters
teamIdinteger · min: 1Required

The ID of the team.

Body
aiMappingAccountIdinteger | nullableOptional

ID of the account used for AI mapping

aiMappingModelNamestring | nullableOptional

Name of the AI model used for mapping

Responses
200
Successful response
application/json
patch
PATCH /api/v2/teams/{teamId}/llm-configuration HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 55

{
  "aiMappingAccountId": 123,
  "aiMappingModelName": "gpt-4"
}
200

Successful response

{
  "aiMappingAccountId": 123,
  "aiMappingModelName": "gpt-4"
}
PreviousSSO certificatesNextTeams > User team roles