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. .
Returns information about the team with the specified teamId.
The ID of the team.
22Specifies 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.
{"value":["id","name","organizationId","activeScenarios","activeApps","operations","transfer","operationsLimit","transferLimit","consumedOperations","consumedTransfer","isPaused"]}Successful response
Deletes the team with the specified teamId. Make also deletes all data associated with the team, for example scenarios, webhooks or custom team variables.
The ID of the team.
22Set this parameter to true to confirm the team deletion. Otherwise, the API call returns an error and the team is not deleted.
trueSuccessful response
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.
The ID of the team.
22The name of the custom variable.
userIDSuccessful response
Gets the list of teams in the organization with specified organizationId.
The ID of the organization.
1Specifies 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.
The value that will be used to sort returned entities by.
The value of entities you want to skip before getting entities you need.
The sorting order. It accepts the ascending and descending direction specifiers.
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.
Successful response
Create a new team in the organization with the specified organizationId.
The name of the team.
The ID of the organization.
The maximum number of operations allowed for the team.
Successful response
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 for Make pricing plans overview.
The ID of the team.
22Successful response
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 for Make pricing plans overview.
The ID of the team.
22The name of the custom variable.
userIDSet to true to confirm deleting the custom variable. Otherwise the API call fails with the error IM004 (406).
trueSuccessful response
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 .
The ID of the team.
22When set to true, the endpoint will calculate and return usage data based on the organization's timezone instead of the user's local timezone.
trueSuccessfully retrieved usage data
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 for Make pricing plans overview.
The ID of the team.
22Number representing the type of the custom variable. The mapping of typeId and variable types is as follows:
number,string,boolean,datein ISO 8601 compliant format YYYY-MM-DDTHH:mm:ss.sssZ. For example: 1998-03-06T12:31:00.000Z.Value assigned to the custom variable.
The name of the variable. You can use letters, digits, $ and _ characters in the custom variable name.
Successful response
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 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.
The ID of the team.
22The name of the custom variable.
userIDNumber representing the type of the custom variable. The mapping of typeId and variable types is as follows:
number,string,boolean,datein ISO 8601 compliant format YYYY-MM-DDTHH:mm:ss.sssZ. For example: 1998-03-06T12:31:00.000Z.Value assigned to the custom variable.
Successful response