Organizations are main containers that contain all teams, scenarios, and users. The API endpoints discussed further allow you to manage organizations. .
Retrieves detail information of the organization with the specified organizationId.
The ID of the organization.
11Set this parameter to true if you are using the API call GET /organizations/{organizationId} shortly after creating the organization. The API call will first check synchronization of the Make backend and your Make zone data. If you don't use this argument, the API call might fail with an error due to unfinished data synchronization. The default value of this argument is false.
trueSuccessful response
Deletes the organization with the specified organizationId. Make also deletes all the teams in the organization.
You can only delete organizations that are associated with your current Make zone. Your current Make zone is specified in the API call URL. Currently, it is either:
eu1.make.com
us1.make.com
The ID of the organization.
11Set to true to confirm the organization deletion. Otherwise, if the organization has active scenarios, Make won't delete the organization and the API call returns an error.
trueSuccessful response
Get list of custom apps associated with the users in the organization. The request response contains information of both published and unpublished custom apps. The custom app name is suffixed with a random text string.
The ID of the organization.
11Successful 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
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 organization.
11The name of the custom variable.
userIDSuccessful response
Retrieves a collection of all organizations, in which the user has membership. The response contains information about the organization name, organizationId and timezoneId. You can get more data about the user organizations with specifying the cols[] query parameter.
However, the values for parameters license, serviceName and isPaused are returned only for organizations in your current Make zone.
Returned organizations are sorted by the organization name in ascending order by default. You can specify sorting order with the query parameter pg[sortBy].
The URL of your Make instance domain.
eu1.make.comMake White Label product instances use the externalId parameter for security reasons. This parameter has null value in the public Make Cloud instance.
{"value":"TESTORG003"}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.
{"value":["id","name","countryId","timezoneId","license","zone","serviceName","teams","isPaused","externalId","productName"]}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 organization using the data sent in the request body. Successful response contains all information about the created organization.
The name of the organization.
ID of the Make region instance associated with the organization. Get the list of Make regions with the API call GET /enums/imt-regions.
The ID of the timezone associated with the organization. Get the list of the timezone IDs with the API call GET /enums/timezones.
The ID of the country associated with the organization. Get the list of the country IDs with the API call GET /enums/countries.
Successful response
Updates the organization data with the values in the request body. If you don't use a parameter in the request body, Make won't change its value. You can update organization name, timezone, and country with the name, timezoneId, and countryId parameters.
Check the available values for the timezoneId and countryId parameters with the API calls GET /enums/timezones and GET /enums/countries.
The request response returns all organization data.
The ID of the organization.
11The new name of the organization.
The ID of the country associated with the organization. Get the list of the country IDs with the API call GET /enums/countries.
The ID of the timezone associated with the organization. Get the timezoneId values with the API call GET /enums/timezones.
Successful response
Invite a user to the organization. To automatically add the user to teams, specify IDs of the teams. The user gets the team role member. You can change the user team role with the API call POST /users/{userId}/user-team-roles/{teamId}.
The ID of the organization.
11The ID of the user organization role assigned to the invited user. Get list of user role IDs from the API call GET /users/roles.
The user registration email.
The user name visible in the team and organization interface.
Note added to the invitation.
The list of team IDs to which the invited user will be assigned. The invited user will receive the team role member.
Successful response
Retrieves the collection of organization variables. The response contains all organization 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}. 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 organization.
11Successful response
Deletes organization variable.
If you don't have the custom variables feature available then the API call returns the error 404. Check the availability of the custom variables feature with the API call GET /organizations/{organizationId}. 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 organization.
11The 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 across all scenarios within all teams in the specified organization for 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 organization.
11When 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 organization variable. You can check the availability of the custom variables feature with the API call GET /organizations/{organizationId}. 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 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 organization.
11Number 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 organization 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}. 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 organization.
11The 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