Organizations
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.
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"}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
Successful response
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.
The name of the organization. The name may contain only letters, numbers, spaces, and the following special characters: ', -, ., (, ), *, +, ,, @, _, /. The name must not start or end with a space.
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
Successful response
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.
bf1effe1-bc9d-4ab3-9414-9c3b66175305Successful response
Successful response
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.
Successful response
Successful response
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.
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
Successful response
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.
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
Successful response
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.
The ID of the organization.
11The new name of the organization. The name may contain only letters, numbers, spaces, and the following special characters: ', -, ., (, ), *, +, ,, @, _, /. The name must not start or end with a space.
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
Successful response
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.
The ID of the organization.
11Successful response
Successful response
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.
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
Successful response
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.
Successful response
When the pause becomes effective (end of the current paid period). Null when not paused.
Scheduled auto-resume date. Null when not paused.
True while the pause is in effect (subscription.pause_applied is true).
Successful response
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.
Successful response
Successful response
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.
Successful response
Successful response
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.
Successful response
Successful response
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.
Date when the subscription should automatically resume. Must be after the current period end and within 12 months.
Successful response
Successful response
Resume the subscription (cancel scheduled pause or resume now)
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.
Successful response
Successful response
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.
The ID of the organization.
Successful response
Successful response
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.
The ID of the organization.
Successful response
Successful response
Delete a payment method
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.
The ID of the organization.
The ID of the payment method.
Successful response
1Successful response
Set default payment method
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.
The ID of the organization.
The ID of the payment method.
What to set as default. Defaults to 'both'. 'extras' and 'both' throw 400 if the payment method is not immediate. 'subscription' sets default for subscription only.
Successful response
Successful response
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.
Successful response
Successful response
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.
The ID of the organization.
10Successful response
Successful response
Claim cancellation offer
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.
The ID of the organization.
10Successful response
1Successful response
Redeem universal discount on current plan
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.
The ID of the organization.
10The ID of the dormant universal discount to redeem
42Successful response
1Successful response
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.
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. The name may contain only letters, numbers, spaces, and the following special characters: ', -, ., (, ), *, +, ,, @, _, /. The name must not start or end with a space.
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
Successful response
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.
The ID of the organization.
11Successful response
Successful response
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.
The ID of the organization.
11Number 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 formatYYYY-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
Successful response
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.
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
Successful response
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.
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:
- 1:
number, - 2:
string, - 3:
boolean, - 4:
datein ISO 8601 compliant formatYYYY-MM-DDTHH:mm:ss.sssZ. For example:1998-03-06T12:31:00.000Z.
Value assigned to the custom variable.
Successful response
Successful response
History of custom variable updates
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.
The ID of the organization.
11The name of the custom variable.
userIDSuccessful response
Successful response
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.
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
Successfully retrieved usage data
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.
The ID of the organization.
11The feature control name.
Make AI ToolsSuccessfully retrieved feature controls
Successfully retrieved feature controls
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.
The ID of the organization.
11The ID of the feature control.
Indicates whether the feature control is enabled (true) or disabled (false).
Successful response
Successful response
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.
The ID of the organization.
11Set to true to enable TFA enforcement for the organization, or false to disable it.
Successful response
Bad request - TFA enforcement feature is not available
Payment required - Upgrade your plan to use TFA enforcement feature
Forbidden - Insufficient rights to modify organization settings
Get the organization's private-spaces settings
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.
The ID of the organization.
11Successful response
Forbidden - Insufficient rights to view organization settings
Organization not found
Update the organization's private-spaces settings
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.
The ID of the organization.
11Required when enabling/disabling auto-creation, toggling admin observers, or bulk-updating existing limits.
trueWhen true, new members of the organization automatically get a private space.
Default operations limit applied when a private space is auto-created. Pass null to set unlimited operations.
When true, applies defaultOperationsLimit to every existing private-space team in the organization. Requires defaultOperationsLimit to be provided in the same request (rejected with IM005 otherwise).
When true, organization admins/owner are added as Team Observer to private spaces (and to all existing ones); when false, those implicit observers are removed. Settable by the organization owner only — a non-owner request including this field is rejected with IM002. Enabling requires the privateSpacesObservability license (rejected with SC402 otherwise).
Successful response
IDs of private-space teams created by enabling auto-creation. Empty unless privateSpacesAutoCreationEnabled was set to true.
IDs of private-space teams whose limits were overwritten by the bulk update. Empty unless bulkUpdateExistingLimits was set.
IDs of private-space teams that were deleted as part of disabling auto-creation. Empty unless privateSpacesAutoCreationEnabled was set to false.
IDs of private-space teams that gained admin Team Observer memberships. Empty unless addAdminsAsObservers was set to true.
IDs of private-space teams that had admin Team Observer memberships removed. Empty unless addAdminsAsObservers was set to false.
Bad request - Invalid body
Payment required - The organization lacks the privateSpacesObservability license needed to enable admin observers
Forbidden - Insufficient rights to modify organization settings, or a non-owner attempted to change addAdminsAsObservers
Confirmation required for a bulk change
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.
The ID of the organization to check permissions within.
123The name of the team permission to check. This should be a valid company/team permission name (e.g., 'scenario add', 'scenario view', 'team view', 'connection add').
scenario addSuccessfully checked permission
Indicates whether the user has the specified permission on at least one team within the organization.
Bad request - missing or invalid teamPermission parameter
User is not logged in
Access denied - user does not have access to the organization
Last updated