Make

Deletes the specified organization. All data associated with the organization and with the teams in the organization, such as data stores and scenarios, are also deleted. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Removes the active or dormant universal discount from the organization. Active discounts are terminated and the Stripe coupon is removed. Dormant discounts are expired. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Deletes the team with the specified `teamId`. Make removes all users from the deleted team and deletes all data associated with the team, such as data stores and scenarios. The team won't be visible for the users. However, if you run the API call `GET /admin/teams` the response will contain also the deleted team with the `deleted: true` pair. Similarly, the team will remain visible in the Administration UI. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Deletes the user with the specified `userId`. Use the `deleteConnections` query parameter to delete the user's connections too. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Removes an agent with a given ID.

Delete an agent by its ID.

Delete a context by its ID.

Cancels a running browser context setup flow: releases the remote browser session and, for a create flow, deletes the not-yet-adopted browser context. Only the user who started the flow can cancel it. Available only when the `is_ai_browser_contexts_enabled` feature flag is enabled.

Deletes a connection with a given ID and returns the ID in the response.

Deletes the given Credential Request.

Deletes the specified custom property structure item. Use the `confirmed` parameter to confirm deleting the structure item. When you delete a custom property item, Make deletes the data filled in the item as well. Deleting custom property item data is irreversible.

Deletes data stores with given IDs and returns their IDs in the response. This endpoint allows deleting one or more data stores at once.

Deletes records from the specified data store. Specify the `keys` of the records you want to delete in the `keys` array in the request body. Use the `all` parameter in the request body to delete all records from the data store. You have to add the `confirmed` parameter in the API call query to confirm deleting the data, otherwise you get an error. When you are deleting all records, you can use the `exceptKeys` parameter to specify keys of the records which you want to keep. The response contains keys of the deleted records.

Deletes a data structure with a given ID and returns the ID in the response.

Errors:<br /> IM004 - Confirmation required (error with metadata) - needs confirmation<br /> IM405 - Device can't be deleted because it contains messages in queue (error with metadata) - needs confirmation<br /> IM005 - Device is locked by a running scenario and thus can't be deleted.

"ids" and "all" can no be used together<br /> "ids" or "all" has to be set<br /> "exceptIds" is possible to use only with "all"<br /> It could happen, that some incoming messages are deleted and others not. In this case, the API returns a successful status code, and the response additionally contains an error object with a error description.

"ids" and "all" can no be used together<br /> "ids" or "all" has to be set<br /> "exceptIds" is possible to use only with "all"<br /> It could happen, that some incoming messages are deleted and others not. In this case, the API returns a successful status code, and the response additionally contains an error object with a error description.

Deletes incomplete executions of the specified scenario. Specify the incomplete execution ID values in the `ids` array in the request body to delete the specified incomplete executions. You can set the `"all": true` pair to delete all incomplete executions of the specified scenario. If you use the `"all": true` parameter, you have to specify the `confirmed=true` query parameter to confirm the deletion. Otherwise, the API call returns the error IM004 (406). Add the `exceptIds` array to the request body to specify items you don't want to delete. You get an error if you try to delete incomplete executions which are being processed. The rest of the specified items is still deleted.

Required scope: datastores:write. DEPRECATED by Make; prefer the non-deprecated sibling.

Deletes the custom function. The response contains information whether the custom function is deleted or not. If you or any of your team members use the custom function in a scenario you have to use the `confirmed` parameter to confirm the custom function deletion. Otherwise, you get an error with a list of scenarios that use the custom function.

Deletes a hook with a given ID and returns the ID in the response.

Deletes items from the processing queue of the specified webhook. Specify the payload ID values that you want to delete in the request body in the `ids` array. You can set the `"all": true` pair to delete all items from the webhook processing queue. If you use the `"all": true` parameter, you have to specify the `confirmed=true` query parameter to confirm the deletion. Otherwise the API call returns the error IM004 (406). Add the `exceptIds` array to the request body to specify items you don't want to delete. The API call response will contain an error message if some of the specified queue items cannot be deleted. The rest of the specified items will be deleted. Deleting a webhook queue item is not allowed when the item is already being processed by the webhook.

Deletes the specified key. Use the `confirmed` parameter to confirm deleting the key. Otherwise, you get an error and the key is not deleted.

Deletes notifications with given IDs and returns their IDs in the response. This endpoint allows deleting one or more notifications at once.

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`.

Cancel the active subscription.

Deletes a payment method from the organization's subscription.

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 Make pricing page (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

Permanently removes an outbound webhook subscription. The webhook stops receiving deliveries immediately. Endpoint is proxy for the Outbound Webhooks service. Full schema documentation is available at https://github.com/integromat/outbound-webhooks/blob/master/openapi/openapi.json.

Deletes a team label. Requires `scenario edit` on the label's team. Removes the label from every scenario it was assigned to.

Removes a team label from a single scenario. Idempotent.

Deletes a scenario with a given ID and returns the ID in the response.

Deletes a buildtime variable with a given value for a scenario with a given ID and returns `OK` in the response.

Deletes custom properties data. Deleting custom properties data is irreversible. Use the `confirmed` parameter to confirm deleting the data, otherwise you get an error and the data are not deleted.

Deletes a scenario note with a given ID and returns the ID in the response.

Discards a scenario recovery snapshot for a given scenario. scenarioId = 0 is a sentinel for unsaved draft scenarios (no ownership check required). Deletes the team-scoped recovery key.

Deletes a scenario folder with a given ID and returns the ID in the response. Scenarios in the deleted folder and its subfolders are moved to the deleted folder's parent, or uncategorized when deleting a top-level folder. Descendant folders are deleted.

Deletes a shared scenario and returns the ID in the response.

Delete App.

Deletes an endpoint. Only possible while the app is not public — once the app is public, endpoints can no longer be deleted; archive them instead.

Removes a connection (account) from the endpoint's list of attached connections.

Delete Function.

Unbinds the app version from the GitHub repository. The repository itself and its contents are never touched — only the binding record in Make is removed. Only the app's author (or an administrator) may delete bindings.

Delete Module.

Delete RPC.

Deletes a connection. The connection must not be in use (e.g. referenced by a webhook/module/RPC or attached to an endpoint), otherwise the request is rejected.

Delete Webhook.

Removes the stored company logo. Succeeds with `204` even when no logo was stored — and in that case does not create a publisher profile. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

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

Removes a user from a connection's access list. Requires `entity manage`. Returns `404` if the user is not on the access list, and `409` if removing them would leave the connection without an Entity Admin.

Removes a user from a key's access list. Requires `entity manage`. Returns `404` if the user is not on the access list, and `409` if removing them would leave the key without an Entity Admin.

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 (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

Deletes a template with a given ID and returns the ID in the response.

Deletes an existing custom role. Only custom-managed roles can be deleted. The role must not be currently assigned to any users.

Delete a specific OAuth connection for the currently authenticated user.

Removes the user's app pin in the specified organization. Does NOT delete the user's module pins under this app — those rows survive so re-pinning the app restores them. Idempotent — unpinning a non-pinned app is a no-op.

Removes the user's module pin in the specified organization. Does not affect the parent app pin. Idempotent — unpinning a non-pinned module is a no-op.

Returns the recorded installation attempt history for a single native app, ordered by most recent first. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Returns the active experiments configuration for the specified organization, as provided by the cashier service. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Get logs for given app. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Gets the list of all organizations in the Make White Label product instance. The response contains all available information about all organizations in the Make White Label product instance. Use the `id`, `name` or `externalId` query parameters to limit the results to a specific organization or the `cols[]` parameter to get specific columns. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Get list of billing audit logs for given organization. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Retrieves available universal discount options for the organization. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Looks up organizations by exact numeric ID or partial, case-insensitive name. Exactly one of `id` or `name` is required. Because organization names are not unique and are matched partially, this returns a capped list of minimal projections (`id`, `name`, `deleted`) used to navigate to the organization detail. Soft-deleted organizations are included. An empty list is returned when nothing matches. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Gets the default organization license for your Make White Label instance. Make uses the default organization license when you create a new organization without specifying the organization's license. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Gets the list of teams in the organization with the specified `organizationId`. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Gets the list of users in a team or an organization. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Gets the list of available admin roles. Admin roles define the permissions that users have at the instance level in the Make White Label product. Refer to the user admin roles documentation (https://www.make.com/en/help/white-label/manage-organizations#instance-level-roles-1628394) for the full breakdown of the user admin roles permissions. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Retrieves general info about accumulated commissions of the specified user. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Retrieves detailed data about individual commisions of the specified user. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Retrieves graph data for commisions in the past year for the specified user. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Retrieves a collection of all users in your Make White Label instance. Use the API call query parameters to limit the results to a user name or user email. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Looks up a single user by exact numeric ID or exact email match (case-insensitive). Deleted users are always included. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Retrieves general info about accumulated commissions of the current user.

Retrieves detailed data about individual commisions of the current user.

Retrieves graph data for commisions in the past year for the current user.

Retrieves a collection of agents for a company with a given ID.

Retrieves an agents for a agent with given ID.

Retrieve a list of all agents.

Retrieve an agent by its ID.

Retrieve a list of all context for an agent.

Retrieve a list of all LLM providers.

Retrieve details of a specific LLM provider by ID.

Retrieve a list of models for a specific LLM provider by ID.

Polls the status of a running browser context setup flow. Only the user who started the flow can read it. A flow that has expired, completed, or been cancelled responds with `404`. Available only when the `is_ai_browser_contexts_enabled` feature flag is enabled.

Gets analytics data for the specified organization. This feature is available only for organizations with the Enterprise plan. You can get analytics data only for organizations where you have the "Owner" organization role. Otherwise, you get the 403 error. The data entries in the response are sorted by the amount of operations used by a scenario in ascending order. Specify different sorting with the `sortBy` parameter. You can use query parameters (like `timeframe[dateFrom]`, `timeframe[dateTo]` or `teamId`) to refine the results and pagination to navigate through a large number of entries. Make keeps the analytics data for a maximum of 30 days for non-Enterprise plans and 60 days for Enterprise plans. The default time frame reflects the maximum available for your plan.

Gets details of the audit log entry with the specified UUID.

Gets a list of all audit log entries for the specified organization. The audit log entries in the response are sorted by the `triggeredAt` property in descending order by default. You can use pagination to navigate through a large number of entries. You can get the audit log entries only for organizations in which you have the "Admin" or "Owner" roles. Otherwise, you get the 403 error.

Gets available audit logs filters for the organization. You can use the data in the response to filter audit log entries you get from the `GET /audit-logs/organization/{organizationId}` endpoint.

Gets a list of all audit log entries for the specified team. The audit log entries in the response are sorted by the `triggeredAt` property in descending order by default. You can use pagination to navigate through a large number of entries. You can get the audit log entries only for teams in which you have the "Team Admin" role. Otherwise, you get the 403 error.

Gets available audit logs filters for the team. You can use the data in the response to filter audit log entries you get from the `GET /audit-logs/team/{teamId}` endpoint.

Get price detail.

Get list of cashier products.

Proxies imt-cashier's VAT-ID format patterns (EU + Northern Ireland). Each entry is keyed by ISO 3166-1 alpha-2 country code (Northern Ireland is keyed under `GB`, Greece under `GR`) and contains: `prefix` — the VAT-ID prefix used in the full ID (equals the ISO code except `GB` → `XI` and `GR` → `EL`); `regex` — an anchored (`^…$`) regex matching the full VAT ID including the optional prefix, safe to use directly via `new RegExp(regex)`; `description` — a human-readable format hint; and `example` — an example VAT ID suitable as a placeholder. Intended for client-side VAT ID format validation.

Retrieves a collection of all connections for a team with a given ID. Returned connections are sorted by name in ascending order.

Retrieves details of a connection with a given ID.

Gets a list of connection parameters that can be updated. You can update a connection with the API call `POST /connections/{connectionId}/set-data`. If the connection cannot be updated then the API call returns the error message "Cannot edit this connection." When this happens, create a new connection instead.

List consumption reports for specified time range and organization. Endpoint is proxy for the Pacman API. Documentation is available at https://github.com/integromat/make-pacman/blob/master/openapi/openapi.json. NOT CALLABLE with this connection's API token: it requires `pacman:use`, which no Make API token can be minted with.

Returns aggregated consumption totals per source type for the requested period, scoped to an organization or a single team within it. Endpoint is proxy for the Pacman API. Documentation is available at https://github.com/integromat/make-pacman/blob/master/openapi/openapi.json. NOT CALLABLE with this connection's API token: it requires `pacman:use`, which no Make API token can be minted with.

Retrieves all modules with credential requirements for a specific app and version. For each module, this endpoint returns: - Module identification (`id`, `name`, `label`) - Required credential type (e.g., `account:slack2`) - OAuth scopes required by the module - Whether the module is a hook-based trigger Custom/SDK Apps: To query custom (SDK) apps, prefix the app name with `app#` (URL-encoded as `app%23`). For example: `/credential-requests/apps/app%23my-custom-app/1/modules-with-credentials`.

Retrieves a list of Credential Requests.

Retrieves a single Credential Request.

Retrieves detail of a single Credential Request with associated credentials. This endpoint has been enhanced to include all credentials associated with the request in a single response, eliminating the need for additional API calls.

Gets a list of custom properties structures in the organization.

Gets the list of structure items in the specified custom properties structure. Use the API call `GET /custom-property-structures?{organizationId}` to get the ID of the custom property structure.

Retrieves a collection of all data stores for a team with a given ID. Returned data stores are sorted by name in ascending order.

Retrieves details of a data store with a given ID.

Retrieves a collection of all records from a data store with a given ID. Each returned record consists of the `key` (custom or automatically generated) and `data`.

Retrieves a collection of all data structures for a team with a given ID. Returned data structures are sorted by name in ascending order.

Retrieves a data structure with a given ID.

Get config of current zone.

Get a list of devices of a given team.

The ID can be id or udid.

Required scope: devices:read.

Required scope: devices:read.

Required scope: devices:read.

Required scope: devices:read.

Required scope: devices:read.

Retrieves the list of incomplete executions of the specified scenario. Supports optional server-side filters — combine any of them to narrow down the results.

Gets detail of the specified incomplete execution.

Gets the blueprint of the scenario that caused the incomplete execution.

Gets bundles that caused the incomplete execution.

Gets data about attempts to resolve an incomplete execution.

Gets detail of the specified incomplete execution log.

Gets the list of statuses that Make assigns to custom apps. - `requestAccepted`: Make has received the request for a custom app review. - `inProgress`: The custom app review is in progress. - `feedbackSent`: The Make app developers have sent their feedback to the developer of the custom app. - `completed`: - `waitingForRelease`: - `declined`: The custom app publishing has been declined by Make. The reasons for that could be:.

Gets the list of countries and their `countryId` values in the `id` column. The `countryId` is a required parameter when you create a new organization with the API call `POST /organizations`.

Gets the list of Make regions and their `regionId` values in the `id` column. The `regionId` is a required parameter when you create a new organization with the API call `POST /organizations`.

Gets the list of Make zones and their `zoneId` values in the `id` column. The `zoneId` is a required parameter when you create a new organization with the API call `POST /organizations`.

Gets the list of languages and their language codes.

Gets the list of locales and their `localeId` values and locale codes.

Gets the list of module types.

Gets the list of all existing organization features and their descriptions.

Gets the list of timezones and their `timezoneId` values.

Gets the list of US states and their `id` values along with the two-letter state `code`.

Gets the list of all of the existing user API token scopes. For more information about the user API scopes refer to the Authentication section (../../authentication/api-scopes-overview.md).

Gets the list of available email notification settings and their `notificationId` values. The language of the notification settings descriptions is set according to user language settings by default. You can specify a different language for the notification settings descriptions with the `language` parameter.

Gets the list of all existing user features and their descriptions.

Retrieves the mapping of custom variable types and their `typeId` values.

Returns historical parallel execution usage metrics for an Organization over a time range, aggregated into samples at a fixed rollup interval. The sample with the highest capacity utilization is picked for each time interval.

Returns a single, real-time snapshot of parallel execution slot usage for an Organization — how many execution slots are currently acquired per scenario, the total slots in use, and the Organization's slot limit. Unlike the historical metrics endpoint, this reflects the live state at the moment of the request.

Retrieves a list of custom functions available in the team. The response contains `id`, `name`, `description` and a brief updates history of all custom functions available in the team. Check availability of the custom functions feature with the API call `GET /organizations/{organizationId}` for the organization to which the team belongs. If the response contains `"customFunctions": true` pair in the `license` object then you have access to the custom functions feature. Refer to the Make pricing page (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

Gets detailed information about a custom function. The response contains function `name`, `code`, a list of scenarios which use the custom function and the custom function's history of updates.

Gets history of updates of the specified custom function. The response contains a list of code changes, the change author and date when the author made the change.

Retrieves a collection of all hooks for a team with a given ID. Returned hooks are sorted by ID in ascending order by default. Use `pg[sortBy]` to sort by `name` or `hookName`.

Retrieves details of a hook with a given ID including hooks data.

Retrieves a list of webhook queue items waiting for processing with the specified webhook. The request response contains: - the incoming payload hash - incoming data scope - the size of the data in bytes - timestamp of the moment when the data were placed in the processing queue.

Retrieves detail information about the specified webhook queue item. You can get the webhook queue item ID value with the API call `GET /hooks/{hookId}/incomings`.

Gets webhook processing queue stats. The response contains the number of items in the webhook queue and the webhook queue limit.

Retrieves a list of the specified webhook execution logs. Use the `to` and `from` parameters to filter the returned logs. The response contains: - `statusId`: the status of the webhook execution; `1` means successful execution, `3` means failed execution - `loggedAt`: the moment when Make created the log - `id`: the ID of the webhook execution log.

Retrieves the specified webhook execution log. The response contains: - `statusId`: the status of the webhook execution; `1` means successful execution, `3` means failed execution - `loggedAt`: the moment when Make created the log - `id`: the ID of the webhook execution log - `data`: information about the request, header, and payload sent to the webhook. Some webhooks don't return the `data` object due to their implementation. Most common examples include instant triggers for Slack, Zoom, Intercom and Facebook lead ads apps.

Determines if a hook with a given ID is active and retrieves its properties that provide you with the address of the hook and inform if the hook is attached, what is its learning status, and if it was not used for a long time.

Get sanity check. NOT CALLABLE with this connection's API token: the route is not served on the public API host.

Returns the apps catalog used by the scenario editor's app search. Two response shapes are supported via the `scoredSearch` query flag: - Default (no `scoredSearch`) — flat list of `SearchAppVersion` entries (one per native/SDK package) plus `AddonApp` entries. - `scoredSearch=true` — apps are scored against zone-level and team-level usage to rank common picks higher. Each app aggregates its versions and modules under `versions[].modules[]`, and `versions[].groups[]` carries the rendered grouping for the UI. The scored response is transformed before being returned: 1. Group normalization — `versions[].groups` is normalized so the response always exposes a well-formed grouping. Authored groupings with fewer than 2 groups are discarded and replaced with per-type default groups (`'actions'`, `'triggers'`, …); otherwise authored groups are preserved and orphan modules (those not referenced by any group) are appended to per-type defaults. 2. Module reorganization — modules can be copied or moved across apps according to product-managed rules. A relocated module appears in the target app's `versions[].modules[]` carrying `appName`, `appVersion`, and `theme` fields that point at its source package. The frontend must use these fields (when present) to load the correct source manifest and render the module in its original app's branding, because a module's unique identity is `(parentApp.name, module.name)`.

Deprecated. Use `GET /credential-requests/apps/{name}/{version}/modules-with-credentials` instead. This endpoint continues to work but will be removed in a future release. Retrieves all modules with credential requirements for a specific app and version. For each module, this endpoint returns: - Module identification (`id`, `name`, `label`) - Required credential type (e.g., `account:slack2`) - OAuth scopes required by the module - Whether the module is a hook-based trigger Custom/SDK Apps: To query custom (SDK) apps, prefix the app name with `app#` (URL-encoded as `app%23`). For example: `/imt/apps/app%23my-custom-app/1/modules-with-credentials`. DEPRECATED by Make; prefer the non-deprecated sibling.

All verified and custom apps, that are available to current user or selected organisation.

Returns the catalog of app endpoints a team can actually call right now, considering both the apps available to the team's organization and the connections (accounts) that exist in the team. Covers both native (compiled) packages and SDK apps; results are grouped by package and version. An endpoint is included when: - its app is available to the team's organization (installed / public), and - either it requires no connection at all (no attached account — usable without authentication), or the team has at least one connection of a matching account type whose granted OAuth scopes cover the scopes the endpoint requires. For each returned endpoint, `credentialsRequired` indicates whether the endpoint needs a connection at all, and `credentialsAvailable` lists the concrete connections in the team that satisfy it (empty for endpoints that need no connection). Private and deprecated endpoints are excluded, except that the app's author always sees their own (non-public and deprecated) endpoints. By default the caller's pending annotation changes are reflected for endpoints of apps they author. DEPRECATED by Make; prefer the non-deprecated sibling.

Returns an IMT Form for testing an SDK (`app#name`) or native app Endpoint. Requires TEAM_VIEW for the supplied team (ORGANIZATION_VIEW for admin requests), runtime app access for SDK apps, and the endpoint-execution feature flag. Native endpoints are resolved directly, including private and deprecated definitions. SDK authors see pending input, attached-account and scope edits; other callers see published values. The required `connectionId` account field is omitted when there are no attached accounts. Its `options.scope` maps each resolved account type (including SDK aliases) to that endpoint's required OAuth scopes. Native account types can require different scopes. Connection-default scope injection remains in the existing connection backend flow. `input.spec` contains the endpoint input fields, expanded from JSON Schema where supported, and is always present, including when empty. Hidden fields preserve the execution coordinates and authorized team. Version lookup and submission use the numeric major version. The Test button submits the complete JSON values directly to POST /endpoints/execute, without an RPC data wrapper. The response omits multipart because this form uses JSON. DEPRECATED by Make; prefer the non-deprecated sibling.

Returns the runtime configuration derived from the current zone and API configuration: the host to use, the OAuth redirect base, redirect/static domains, default locale, support contact, and brand. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Retrieves a single data structure (UDT) by id, including its spec. Intended for service-to-service callers (ISC JWT) that do not carry user identity. The team-scoped, permission-checked variant is `GET /data-structures/{dataStructureId}`. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Retrieves basic enrichment data for a list of device IDs. This endpoint is designed for internal services that need to enrich their data with device information including device ID, UDID, and associated team ID. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Retrieves details for specified organizations by their IDs. You can specify which columns to return using the `cols[]` query parameter. If `cols[]` is not provided, all available details for the organizations are returned. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Returns the canonical execution-time organization projection used by scenario blueprint finalization and RPC workers. Values are derived from `users.organization.license` and `users.organization.product_flags` via `scenarios.blueprint_finalize_internal_organization`. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Retrieves the pause status of the organization with the specified `organizationId`. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Finds the private space (single-user team) a user owns within an organization. When `accountName` is given, `hasAccount` in the response reports whether the space already has a `users.companyAccount` row with that `account_name` — this lets a caller avoid re-creating a connection that already exists. When `accountName` is omitted, `hasAccount` is `null` ("not evaluated"), not `false` — a caller that doesn't ask for the check should not read `false` as "checked and absent". NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Get scenario executions list. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Returns a list of scenarios belonging to a team for ISC consumers (e.g. make-adapter). Requires a valid ISC JWT signed by the caller's shared secret. Full mode (no `updatedSince`): returns all non-deleted, non-tool scenarios. Delta mode (`updatedSince` provided as epoch-ms): returns every scenario whose `lastEdit` is >= that timestamp, including soft-deleted ones (`isDeleted: true`). Soft-deletes bump `lastEdit`, so deletions ride the same delta response without a separate reconcile pass. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Reports whether the SDK app version has an `apps.access` row for the organization — the runtime gate the Executor checks before running one of the app's Endpoints, because that execution is billed to this organization. Deliberately stricter than the `apps.app_check_access` routine used elsewhere: authorship of the app, its `opensource` flag and admin rights all grant no pass. Only an explicit installation in this organization counts. A missing installation is reported as `installed: false` with a `200`, not a `403` — the caller owns the resulting status and message, which is what lets the Executor name both the app and the organization in its own error. The organization's deletion state is not checked: `apps.access` keeps its row when an organization is soft-deleted, so a caller that cares must check that separately. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Retrieves details for specified organizations by their IDs. You can specify which columns to return using the `cols[]` query parameter. If `cols[]` is not provided, all available details for the organizations are returned. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Reports whether the team already has a `users.companyAccount` row with the given `accountType` (the `account_name` column). Lets a caller check before calling `POST /internal/teams/{teamId}/connections`, reducing (not eliminating) the chance of a duplicate — this check and a later create are not atomic, and `users.companyAccount` has no unique constraint on `(company_id, account_name)`. Best-effort, not a guarantee: a caller that must guarantee at most one connection needs its own coordination on top of this. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Retrieves the pause status of the team with the specified `teamId`. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Retrieves the features enabled for a specific user by their `userId`. This endpoint is for internal service-to-service communication using ISC authorization. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Resolves an email to a Make user id for internal service-to-service communication using ISC authorization. Soft-deleted and suspended users are treated as non-existent. Responds with `userId: null` (not 404) when no active user matches — an unmatched email is an expected outcome, not an error. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Validates a forwarded Make browser session and returns its authenticated user ID. This endpoint is available only to ISC-authorized internal services. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Gets the list of keys in your custom keychain. You can use the `typeName` query parameter to filter your keys based on their type. Run the list of key types (./get--keys--types.md) API call to get a list of available key types.

Gets details of the specified key.

Gets the list of available key types.

Get team preferences.

Get preferences.

Retrieves a collection of all notifications for the authenticated user. Returned notifications are sorted by ID in descending order.

Retrieves details and full content of a notification with a given ID.

Authorize.

Oauth Callback.

Oauth Callback Id.

Extend.

Reauthorize.

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].`.

Retrieves detail information of the organization with the specified `organizationId`.

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.

Checks if the current user has a specific team (company) permission on any team within the specified organization. Returns `hasPermission: true` if the user has the permission on at least one team in the organization, otherwise returns `hasPermission: false`.

Retrieves all feature controls for the specified organization. Response order of the feature controls is by descending ID.

Retrieves the collection of child organizations. If no organization found response will contain empty array in `managedOrganizations` variable. Refer to the MMS page (https://help.make.com/make-managed-services-mms) for Make Managed Services (MMS) overview.

Retrieves the collection of child organizations with consumption of opertaions/credits. If no organization found response will contain empty array in `managedOrganizationsConsumption` variable. Refer to the MMS page (https://help.make.com/make-managed-services-mms) for Make Managed Services (MMS) overview.

Get list of past payments.

Returns the private-spaces settings for the organization. When the organization has no private-spaces settings configured yet, defaults are returned: - `privateSpacesAutoCreationEnabled` defaults to `false` - `defaultOperationsLimit` defaults to `1000` - `addAdminsAsObservers` defaults to `false` Once configured, the stored value is returned as-is — including an explicit `null`, which means unlimited operations (distinct from the never-configured default of `1000`).

Get all SSO certificates.

Get detail of an active subscription.

Returns a list of available payment method types for the organization's subscription.

Returns a list of payment methods for the organization's subscription.

Retrieve a test clock (TEST ONLY).

Returns the current universal discount (active or dormant) for the organization. The user must have the 'payment edit' organization permission or the 'organization view' admin permission.

Retrieves a list of daily centicredits, 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 Help Center article (https://www.make.com/en/help/general/manage-time-zones).

Retrieves information about all users and their roles in the organization with the specified `organizationId`.

Retrieves information about a user role in an organization with the specified `userId` and `organizationId`. Get all user role IDs with the API call `GET users/roles`.

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 Make pricing page (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

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.

Invitation detail.

Returns the outbound webhook subscriptions belonging to the given organization. Endpoint is proxy for the Outbound Webhooks service. Full schema documentation is available at https://github.com/integromat/outbound-webhooks/blob/master/openapi/openapi.json.

Returns a single outbound webhook subscription belonging to the given organization. The `signingSecret` is not included in this response — it is only returned at creation time. Endpoint is proxy for the Outbound Webhooks service. Full schema documentation is available at https://github.com/integromat/outbound-webhooks/blob/master/openapi/openapi.json.

Pings the Make API service. Successful response contains plain text.

Gets the list of private spaces in the organization with specified `organizationId`.

Returns the details of a single private space. Requires the `personal team own view` organization permission. Non-members receive a 404.

Retrieves the colour-coded labels owned by a team, sorted by name (case-insensitive) ascending. Each label carries a `scenariosCount` — the number of non-trashed scenarios in the team that currently carry it.

Retrieves a collection of all scenarios for a team or an organization with a given ID. Returned scenarios are sorted by proprietary setting in descending order.

Retrieves scenarios that contain at least one AI agent module for the specified team. Results are sorted by last edit date in descending order.

Retrieves all available properties of a scenario with a given ID. The returned details do not include a scenario blueprint. If you want to get a scenario blueprint, refer to the Get scenario blueprint (./blueprints/get--scenarios--scenarioid--blueprint.md) endpoint.

Retrieves a blueprint of a scenario with a given ID.

Retrieves a collection of all blueprints versions for a scenario with a given ID. Due to the regular archiving process, only the versions that are not older than 60 days can be retrieved. Each returned blueprint version consists of the date and time of the blueprint creation, IDs of the blueprint version and related scenario, and the information if the blueprint was created for the draft or live scenario version.

Retrieves buildtime variables of a scenario with the given ID. Buildtime variables could be team or user defined, team defined ones are prefixed with a `TAC_` and user defined variables are prefixed with a `PAC_`. `TAC_`s can be used within the scenario as per its input spec by the entire team, whereas `PAC_`s can only be used within the scenario by the user who added them.

Retrieves basic scenario credits and transfer consumption overview.

Gets custom properties data of the specified scenario.

Verifies whether the module data is set or not. This endpoint doesn't retrieve the module data.

Retrieves details about an execution.

Retrieves the scenario inputs and outputs specification for the specified scenario. Check out the scenario inputs and outputs documentation (https://help.make.com/scenario-inputs-and-outputs) in the Make help center.The scenario inputs and outputs feature is available with all plans. Read more about Make pricing. (https://www.make.com/en/pricing).

Retrieves a collection of all logs for a scenario with a given ID. Returned logs are sorted by `imtId` in descending order. Logs with type `modify` can include versioned Scenario History changes in `detail.change`.

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.

Retrieves enriched execution detail for a given execution. Without `include` the response shape is identical to `GET /scenarios/{scenarioId}/logs/{executionId}`. Use the `include` query parameter to request additional data sections in a single call.

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

Retrieves an aggregated list of operations per module within a specified time period. DEPRECATED by Make; prefer the non-deprecated sibling.

Retrieves a collection of all scenario notes for a team and organization with a given ID. Returned notes are sorted by their id in descending order.

Retrieves all available properties of a scenario note with a given ID.

Retrieves a scenario recovery snapshot if it exists for a given scenario. scenarioId = 0 is a sentinel for unsaved draft scenarios (no ownership check required). Uses team-scoped storage for cross-team draft isolation.

Retrieves properties of a trigger included in a scenario with a given ID. A trigger is a module that is able to return bundles that were newly added or updated (depending on the settings) since the last run of the scenario. An example of a trigger is a hook.

Retrieves a list of daily centicredits, operations, and data transfer usage for a specified scenario 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 (https://www.make.com/en/help/general/manage-time-zones).

Retrieves a list of scenarios and their current consumption. Make counts the number of consumed centicredits, operations, and transferred data according to your reset period. If you have a monthly reset period, the response contains a list of scenarios that consumed at least one hundred centicredits (one operation) in the current reset period with their consumption and data transfer.. <div class="alert alert-warning"> <p>If you have a yearly reset period, the response contains a list of scenarios that consumed at least one hundred centicredits (one operation) in the last 60 days, or from the last reset if that period is shorter than 60 days.</p> <p>60 days after the reset the scenario consumptions turn into running totals over the last 60 days.</p> <p>For example, let's assume that you have a set of scenarios that consume 100000 centicredits (1000 operations) every day. On the 61st day from your last reset, you turn off a scenario that consumes 20000 centicredits (200 operations) every day, reducing your consumption to 80000 centicredits (800 operations) per day.<p> <p>If you would have the yearly reset period and you would be tracking your scenario consumptions, you would get the following data:</p> <div itemscope itemtype="https://schema.org/FAQPage"> <div class="card table"> <table class="table"> <thead> <tr> <th><strong class="text-nowrap">Day</strong></th> <th><strong>Consumptions</strong></th> <th><strong>Delta</strong></th> </tr> </thead> <tbody> <tr> <td>1</td> <td>1000</td> <td></td> </tr> <tr> <td>2</td> <td>2000</td> <td>1000</td> </tr> <tr> <td>3</td> <td>3000</td> <td>1000</td> </tr> <tr> <td>...</td> <td></td> <td></td> </tr> <tr> <td>60</td> <td>60000</td> <td>1000</td> </tr> <tr> <td>61</td> <td>59800</td> <td>-200</td> </tr> <tr> <td>62</td> <td>59600</td> <td>-200</td> </tr> </tbody> </table> </div> </div> <p>The negative difference between scenario consumptions on the 60th and 61st day happens because on the 61st day, the endpoint doesn't collect data from the first day anymore. Your scenario consumptions contain a total over the time period from the second day until the 61st day.</p> <p>For billing, Make uses a different system which ensures accurate billing.<p> </div> Check the parameter `lastReset` in the response for the timestamp of the start of your current reset period. You can also view the end of your current restart period in your dashboard in the Usage reset field. Set the `organizationId` or `teamId` parameters to limit the results to a specific organization or team.

Retrieves direct scenario folder children for a team or organization. Provide teamId or organizationId. If both are provided, teamId is used. Omit parentId to return top-level folders.

Returns completed execution summaries across all scenarios visible to the API token, ordered ascending by completion time. Designed for polling integrations that need a single feed of "what completed since last poll" across the full scenario fleet. Filtering: Only `EXECUTION_END` records are returned (in-progress executions excluded). Pagination: Use `since` as the cursor — store `max(timestamp)` from the last response and pass it as `since` on the next poll. Limit: `since` must not be older than 90 days.

Returns a list of replayable executions for a given scenario.

Returns a paginated list of shared scenarios for a specified organization or team. Supports filtering by title, scenario name, and folder ID. Note: Either `organizationId` or `teamId` must be provided, but not both.

Returns all shares created for the specified scenario.

Get shared scenario detail by ID.

Retrieves the tool configuration from the underlying scenario.

Returns the number of scenarios currently in the trash for a team — scenarios that were deleted and are still within the 30-day recovery window. Useful for rendering a trash badge count. The count respects the same permissions as listing scenarios.

Returns the active category taxonomy the new SDK app review form offers, in display order. The taxonomy is exactly two levels deep (category → subcategory) and is global product configuration — not per app and not per user, so every authenticated caller gets the same list. Identify a pick by its `slug`, not its `name`: that is what `PUT /sdk/apps/{app}/{version}/app-review/form` expects in `categories` / `subcategories`, and it is stable across relabelling. Categories retired by a later catalog sync stop appearing here, but their slugs keep resolving in review forms that already stored them. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

Retrieves a collection of all apps available to the authenticated user.

Get App.

Returns the full state of the new review flow for the app version: the lifecycle phase, the auto-saved draft form, the submitted snapshot, and the review history timeline. Always responds `200` for the app's author — when the new flow has never touched the app, the state is synthesized (`derivedFromLegacy: true`) from the legacy review flags: an approved app reports `approved`, an in-review app reports `review` (or `changes_required` when the legacy reviewer status is "feedback sent"), anything else reports `dormant`. Only the app's author (or an administrator) may read the review state. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

Get Change.

Get app client id and client secret.

Lists the metadata of all endpoints defined on the given app version. The heavy section payloads (`api`, `scope`, `outputParameters`) are excluded by default and are fetched per section. Pass `includeInputSchema=true` to also include each endpoint's `inputParameters` (Forman schema DSL) in the listing. On an approved app with a pending (unreleased) edit to `inputParameters`, the value returned here is the live one, not the pending edit — fetch `GET .../endpoints/{endpoint}/inputParameters` for the up-to-date value.

Returns the metadata of a single endpoint. On approved apps, pending changes are overlaid.

Get App Events Log.

List App Functions.

Get Function.

Lists all GitHub repository bindings of the given app version. Returns an empty list when the app is not bound to any repository. The `remoteHeadSha`, `behindBy` and `syncStatus` fields are refreshed best-effort against GitHub on every call — when GitHub is unreachable or the bound branch has no commits, `remoteHeadSha` is `null` and `syncStatus` degrades to `idle` (or `error` if the last sync failed). Only the app's author (or an administrator) may read bindings.

Returns a single GitHub binding of the given app version. The `remoteHeadSha`, `behindBy` and `syncStatus` fields are refreshed best-effort against GitHub on every call. Responds with `404` when the binding does not exist or belongs to a different app version. Only the app's author (or an administrator) may read bindings.

Reports whether the app version has drifted locally from what was last pushed to GitHub — the "ahead by N changes" signal, independent of whether the remote branch itself has moved (that's the binding's `behindBy`). Combines two signals de-duplicated per component: a checksum diff of the current source tree against the snapshot captured at the last push, and pending change rows that approved public apps accumulate instead of writing directly. Before the first push there is no snapshot (`snapshotAvailable: false`) and every component reports as `added`. Only the app's author (or an administrator) may read the diff.

File-level, three-way diff between the app's local source tree, the bound remote branch HEAD, and the per-file snapshot captured at the last push. Lists only files whose local and remote contents differ, with both contents included for text files so a UI can render a side-by-side view. When a snapshot is available, each entry also reports which side moved since the last push and flags real merge conflicts (both sides moved to different content). Binary files (icons) are listed with SHAs only — their contents are omitted. Files outside the SDK source layout (e.g. the bootstrap `.claude/` tree committed on repository creation) are ignored. Costs one GitHub tree listing plus one contents fetch per differing text file. Only the app's author (or an administrator) may read the diff.

List App Modules.

Get Module.

Get Module Section.

Get App Docs.

Get App Review.

List App RPCs.

Get RPC.

Get RPC Section.

List App Connections.

List App Webhooks.

Get Connection.

Available sections: api, parameters, scopes, scope, install, installSpec<br />.

Get Connection Common.

Get App Invite.

All verified and custom apps returned with theme color.

Get Webhook.

Get Webhook Section.

Returns the calling user's account-level publisher profile ("App developer contact" of the new SDK app review flow), or `null` when the user has no profile yet. The profile is strictly self-scoped — there is no way to read another user's profile. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

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

Returns information about the team with the specified `teamId`.

Returns the access list (entity ACL) of a connection — the principals granted a role on it. A caller holding the `entity use` permission on the connection sees every member; any other member of the connection's team sees only the Entity Admins. The connection must belong to the team in the path. Requires the locked connections feature to be enabled for the organization the team belongs to; otherwise the endpoint returns `400` (`IM903`).

Retrieves all feature controls for the specified organization which the team belongs to.

Returns the access list (entity ACL) of a key — the principals granted a role on it. A caller holding the `entity use` permission on the key sees every member; any other member of the key's team sees only the Entity Admins. The key must belong to the team in the path. Requires the locked connections feature to be enabled for the organization the team belongs to; otherwise the endpoint returns `400` (`IM903`).

Returns every locked connection and key of the team, each with the permissions the calling user holds on it and the part of its access list the caller may see. The `permissions` array reflects the caller's own grants: an entity without `entity use` cannot be referenced in scenarios by the caller. For each entity, a caller holding `entity use` sees the full access list; any other member of the team sees only the `entity manage` holders. The caller must hold the team's connections and keys view permissions. Requires the locked connections feature to be enabled for the organization the team belongs to; otherwise the endpoint returns `400` (`IM903`).

Retrieves a list of daily centicredits, 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 (https://www.make.com/en/help/general/manage-time-zones).

Gets list of all users and their roles in the team with the specified `teamId`. Get all user role IDs with the API call `GET /users/roles`.

Retrieves information about user role in a team with the specified `userId` and `teamId`. Get all user role IDs with the API call `GET users/roles`.

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 (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

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.

Retrieves a collection of all templates for a team with a given ID. Returned templates are sorted by ID in ascending order.

Retrieves details of a template with a given ID.

Retrieves a blueprint of a template with a given ID.

Retrieves a collection of all public (approved) templates that are available for anyone. Returned templates are sorted by usage in descending order.

Retrieves details of a public (approved) template with a given `publicUrl`.

Retrieves a blueprint of a public (approved) template with a given `publicUrl`.

Retrieves a collection of all users for a team or an organization with a given ID. Returned users are sorted by id in descending order.

Returns users who have a specific permission within an organization or team. Use `type: organization` with `organizationId` to find users that hold a given organization-level permission. Use `type: company` with `teamId` to find users that hold a given team-level permission. Requires the `organization users view` permission on the resolved organization. When `type` is `company`, additionally requires the `team view` permission on the specified team.

Gets list of all users and their roles in the organization with the specified `organizationId`. Get all user role IDs with the API call `GET /users/roles`.

Gets information about user role in an organization with the specified `userId` and `organizationId`. Get all user role IDs with the API call `GET /users/roles`.

Gets team roles of the user with the specified `userId`. The response contains user's team role ID for all teams the user is part of. Get the mapping of the `userRoleId` and the user role `name` with the API call `GET /users/roles`.

Gets user role detail in the team with the specified `teamId`. Get the mapping of the `userRoleId` and the user role `name` with the API call `GET /users/roles`.

Retrieves data about the authenticated user. Refer to the `cols[]` parameter accepted values to get more information about the currently authenticated user.

Returns current authorization information for the authenticated user including scope and authentication method used.

Gets the OAuth connections for the currently authenticated user.

Returns whether the authenticated user has a pending onboarding survey. If the survey has been submitted, the response payload is included.

Retrieves organization invitations of the currently authenticated user.

Returns every app the current user has any pin under in the specified organization — pinned apps and apps that only have pinned modules. Each entry carries an `isAppPinned` flag: when `true` the app itself is pinned and shows up in the "My apps" tab; when `false` only modules are pinned and the entry is rendered inside the app-detail panel. App and module pins are independent — pinning a module does not pin its app, and unpinning an app leaves its module pins intact (and they reappear if the app is re-pinned). Pins are scoped per (user, organization) and are version-agnostic — the UI resolves the latest available version of each pinned app/module from the catalog. App names follow the convention used by `GET /imt/apps`: SDK apps are surfaced as `app#<name>`, native apps as the bare package name.

Returns the authenticated user's preference tree. The tree is a `{ [namespace]: value }` object where each top-level key is an independently managed namespace (e.g. `ui`) defined by the shared-preferences library. A user who has never written preferences returns an empty tree. NOT CALLABLE with this connection's API token: it requires `user-preferences:read`, which no Make API token can be minted with.

Get user redirect action.

Gets list of all existing user role names and IDs. Optionally filter by `category`, a specific `roleId`, or pass `organizationId`/`teamId` to include custom roles for that organization. Set the user roles in an organization with the `POST /users/{userId}/user-organization-roles/{organizationId}` API call. Use the `POST /users/{userId}/user-team-roles/{teamId}` API call to set user roles in a team.

Returns the detail of a single role by its ID. For custom-managed roles, requires the `customRoles` license and `ORGANIZATION_USERS_VIEW` permission on the role's organization.

Gets a list of all available permissions that can be assigned to user roles. Use the `roleCategory` parameter to filter permissions by team or organization roles.

Gets the number of unread notifications for the currently authenticated user.

Gets the authenticated user's notification settings for a team specified by the `teamId`. Get the mapping of the `notificationId` and the team notification setting type with the API call `GET /enums/user-email-notifications`. The response only contains the notification types available to the user. Some notification types require a specific team permission — types whose permission the user does not hold are omitted from the response.

Checks the authenticated user's notification settings for the team and notification type specified by the `teamId` and `notificationId`. Get the mapping of the `notificationId` and the team notification setting type with the API call `GET /enums/user-email-notifications`. Only notification types available to the user are returned. Some notification types require a specific team permission — for a type whose permission the user does not hold, the response contains no notification setting.

Preflight an app RPC call.

Updates the specified organization. Updates only parameters specified in the request body. Check the API call to create organizations (https://www.make.com/en/api-documentation/admin-organizations-post) for a full breakdown of the organization license parameters. <div class="alert alert-warning">When updating organization's license, Make replaces the old organization's license with the new one. You have to send a valid <code>license</code> object with all the license parameters you want to set for the organization.</div> You can set the next reset of the organization's consumption with the `nextReset` parameter. Use the `performReset` parameter to reset the organization's consumption with the API call. You can set the next reset with the `nextReset` parameter, or Make sets the next reset according to the organization's `resetPeriod`. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Updates team information. Make updates only the values in the request body. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Updates user information. Make updates only the specified information. In addition, you can set the user admin roles in the `usersAdminsRoleId`. Check the available roles with the API call `GET /admin/users/admins-roles`. Refer to the user admin roles documentation (https://www.make.com/en/help/white-label/manage-organizations#instance-level-roles-1628394) for the full breakdown of the user admin roles permissions. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Updates a new agent with given ID.

Modify an existing agent by its ID.

Updates the specified connection's name. The response contains all information about the updated connection.

Updates the specified item of a custom property structure. Specify the attributes you want to update in the request body. You cannot update the item `name` and `type`. You can get the item ID with an API call to list custom property structure items (./get--custom-property-structures--custompropertystructureid--custom-property-structure-items.md). When you want to update the `options` of a `multiselect` or `dropdown` item, specify all the options for the property. The new set of options replaces the current options.

Updates properties of a data store with a given ID in a team with a given ID by passing new values in the request body. In the response, it returns all details of the updated data store including properties that were not changed. Any property that is not provided will be left unchanged. This endpoint cannot be used to update data included in the data store - for this use the endpoints for managing data stores data (./data/get--data-stores--datastoreid--data.md).

Updates a data store record with a given key by passing new data in the request body. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated data including properties that were not changed.

Updates the specified data structure. Make updates only parameters you send in the request body. Note that when you update the data structure specification with the `spec` parameter, you have to provide all structure fields you want to use. Make replaces the old structure specification with the new one. The response contains all details about the updated data structure.

Update a device.

Updates the specified incomplete execution.

Updates custom functions `description` or `code`. You cannot change the `name` of the custom function. Make sure to use the same function name in the function's `code`. Otherwise, you get an IM005 error. Make validates the custom function's code first. You get an IM005 error if the code validation fails. The validation might fail because of a syntax error in the function's code or when the code uses a JavaScript feature that Make doesn't support. Check the custom functions limitations (https://www.make.com/en/help/functions/custom-functions#limitations-of-custom-functions) in the Make Help center.

Updates a hook with a given ID by passing new values in the request body. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated hook including properties that were not changed.

Updates a key `name`, connection parameters, or both with the data specified in the request body. If you don't specify a parameter, Make keeps the original value. Use the `GET /key-types` API call to find out which parameters you need to specify in the `parameters` object based on the key type.

Updates a native email notification preference of a team for the user associated with the API key used for authentication. Some notification types require a specific team permission. Enabling such a type for a user who does not hold the required permission fails with `403`. Disabling a notification type is always allowed, regardless of permissions or feature flags.

Update team preferences.

Update global preferences.

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.

Enable or disable feature control for the specified organization.

A successful response contains summary of new operation limits for parent and child organization. The `operations` parameter must be a multiple of 10000. Refer to the MMS page (https://help.make.com/make-managed-services-mms) for Make Managed Services (MMS) overview.

Updates the organization's private-spaces settings. All body fields are optional — only the keys provided are written. Confirmation requirement: The `?confirmed=true` query parameter is required when the request includes any of these bulk operations, otherwise the endpoint responds with `IM004`: - `privateSpacesAutoCreationEnabled: true` — bulk-creates a private space for every eligible organization member (those holding the `personal team own view` permission) that does not already own one. - `privateSpacesAutoCreationEnabled: false` — also deletes every existing private-space team in the organization. - `addAdminsAsObservers: true` / `false` — reconciles every existing private-space team: enabling adds org admins/owner as `Team Observer`; disabling removes those implicit observers. - `bulkUpdateExistingLimits: true` — overwrites `limits.operations` on every existing private-space team in the organization to match the `defaultOperationsLimit`, and re-evaluates each team's pause state. `defaultOperationsLimit` must be provided in the same request when `bulkUpdateExistingLimits` is `true` (a number, or `null` for unlimited), otherwise the request is rejected with `IM005`. This ensures the value applied org-wide is stated explicitly rather than implicitly inherited from the org's currently stored setting. Changing `defaultOperationsLimit` alone (to any value, including `null` / `0` / lower) only affects future creations and does NOT require confirmation. License requirement: Enabling `addAdminsAsObservers` requires the organization to hold the `privateSpacesObservability` license parameter. Without it, the request is rejected with `SC402`. Owner-only field: `addAdminsAsObservers` can be changed only by the organization owner. Other organization admins may update the remaining settings on this endpoint, but a request that includes `addAdminsAsObservers` (either `true` or `false`) from a non-owner is rejected with `IM002`.

Change subscription.

Sets a payment method as the default for the organization's subscription.

Enables or disables two-factor authentication (TFA) enforcement for the specified organization. When TFA enforcement is enabled, all users in the organization are required to have two-factor authentication configured. Users who do. not have TFA enabled will be automatically logged out. Note: This endpoint is available only for organizations with a plan that supports TFA enforcement.

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 Make pricing page (https://www.make.com/en/help/general/pricing-parameters) 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_.

Updates a mutable field on an outbound webhook subscription. Only the fields provided in the request body are changed. Endpoint is proxy for the Outbound Webhooks service. Full schema documentation is available at https://github.com/integromat/outbound-webhooks/blob/master/openapi/openapi.json.

Activates a previously paused outbound webhook subscription. The webhook's `status` becomes `live` on success. Endpoint is proxy for the Outbound Webhooks service. Full schema documentation is available at https://github.com/integromat/outbound-webhooks/blob/master/openapi/openapi.json.

Pauses an outbound webhook subscription. The webhook's `status` becomes `paused` on success and deliveries stop until the webhook is activated again. Endpoint is proxy for the Outbound Webhooks service. Full schema documentation is available at https://github.com/integromat/outbound-webhooks/blob/master/openapi/openapi.json.

Sets one operations (credit) limit on up to 100 private spaces of an organization in a single request. This is the bulk counterpart of `PATCH /private-spaces/{privateSpaceId}`. List the target spaces in `privateSpaceIds` (duplicates are ignored). `operationsLimit` is an integer number of credits, or `null` to remove the limit. The transfer limit is derived from the operations limit automatically. A limit of `0` is a real limit: spaces whose limit changes to `0` are paused. Requires the `personal team manage` organization permission (admins: `organization edit`). The operation is all-or-none: every listed id must be an active private space of `organizationId`, otherwise nothing is changed and the call fails with HTTP 404. Lowering the limit to or below a space's current consumption pauses that space. An unconfirmed request that would pause at least one space fails with `IM004` (HTTP 406) whose metadata lists exactly those spaces; re-send with `confirmed=true` to proceed. Spaces whose limit already equals the new value are returned unchanged and emit no audit event. Available on app zones only.

Updates a private space. Currently supports changing the operations limit (credit limit). Requires the `personal team manage` organization permission.

Renames, re-colours, or re-describes a team label. Requires `scenario edit` on the label's team. Every chip using the label updates at once.

Updates a scenario with a given ID by passing new values in the request body. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated scenario including properties that were not changed.

Updates custom properties data of the specified scenario. Make updates only the custom properties data you specify in the request body. The custom property has to contain data already. The update data have to conform to the current custom scenario properties structure. If the initial value is empty, then the API call returns an error. To fill in first values to the custom properties, use the API call to fill in custom properties data (./post--scenarios--scenarioid--custom-properties.md).

Updates specification of the scenario inputs. Check out the scenario inputs documentation (https://www.make.com/en/help/scenarios/scenario-inputs) in the Make help center. If you want to enable the scenario inputs you have to set the scenario scheduling to "On demand" first, otherwise you get error 422 (IM016). You can use the API call: `PATCH /scenarios/{scenarioId}?confirmed=true` with the request body: `{"scheduling": "{\"type\":\"on-demand\"}"}` You can disable inputs for the specified scenario by sending a payload with an empty `input` array. The response contains the updated scenario inputs specification. The scenario inputs feature requires your account to have the pricing plan Pro or higher. Read more about Make pricing. (https://www.make.com/en/pricing).

Updates a scenario note with a given ID by passing new values in the request body. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated note including properties that were not changed.

Updates a scenario folder with a given ID by passing a new name, a new parent folder, or both in the request body. Use parentId null to move the folder to the top level. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated folder including properties that were not changed.

Updates a shared scenario by ID by passing new values in the request body. Any property that is not provided will be left unchanged.

Updates a tool configuration with a given scenario ID by passing new values in the request body. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated tool configuration of the underlying scenario, including properties that were not changed.

Patch App.

Patch app base configuration.

Updates one or more metadata fields of an endpoint. At least one field must be provided. On an approved app, the versioned fields (`context`, `annotations`, `attachedAccounts`) are recorded as pending changes instead of being applied immediately. When `attachedAccounts` is supplied, every connection it lists must belong to the app, otherwise the request is rejected.

Updates editable metadata of an existing GitHub binding — typically the sync branch or the Make connection the binding authenticates through. When `connectionId` is changed, the new connection must be a GitHub connection, otherwise responds with `400`. At least one field must be provided. Only the app's author (or an administrator) may update bindings.

Updates a module.<br />.

Patch RPC.

Update Connection.

Update Webhook.

Creates or updates the calling user's publisher profile with the provided fields (at least one is required; omitted fields keep their value, `null` clears a field). Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

Updates information about the team with the specified `teamId`.

Changes the entity-tier role of a user already on a connection's access list. Requires `entity manage`. Returns `404` if the user is not on the access list, and `409` if the change would demote the connection's last Entity Admin.

Changes the entity-tier role of a user already on a key's access list. Requires `entity manage`. Returns `404` if the user is not on the access list, and `409` if the change would demote the key's last Entity Admin.

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 (https://www.make.com/en/help/general/pricing-parameters) 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_.

Updates a template with a given ID by passing new values in the request body. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated template including properties that were not changed.

Updates a user with a given ID by passing new data in the request body. Any property that is not provided will be left unchanged. As the response, it returns all details of the updated user including properties that were not changed.

Updates the name, description, or permissions of an existing custom role. Only custom-managed roles can be updated.

Applies an RFC 7396 JSON Merge Patch to the authenticated user's preferences. The request body is a `{ [namespace]: object | null }` envelope: `null` deletes the namespace, an object is merged recursively into the stored namespace payload (`null` on any leaf deletes that leaf; other values replace). Behaviour by deployment mode: - Private zones: the merge happens locally against `users.user_preference`. - Public zones: the envelope is forwarded to HQ via swarm; HQ writes and replicates the row back to the local database. Validation is two-stage: `validatePreferencePatch` from `@integromat/shared-preferences` checks the envelope shape, namespace key format, and total byte size, then each non-`null` namespace patch is validated by its own parser registered by the API layer. Unknown namespaces are rejected. NOT CALLABLE with this connection's API token: it requires `user-preferences:write`, which no Make API token can be minted with.

Create a new organization in the Make White Label instance. You can set the organization admin, timezone, country and features with the `countryId`, `timezoneId`, `userOrgAdmin` and `license` parameters in the request body. If you don't use the `countryId` and `timezoneId` parameters Make uses your account values to set the organization timezone and country. If you don't use the `userOrgAdmin` parameter you are set as the organization admin. The `license` object sets the features and limits for the users in the organization. The following table lists all license parameters and their maximum, minimum, or available values for enumerated parameters. If you don't use the `license` parameter Make sets the organization's license to the default values for your Make White Label instance. You can check the default license of your Make White Label instance with the get default license (https://www.make.com/en/api-documentation/admin-system-settings-default-license-get) endpoint. <!-- license input anchor begin --> <div itemscope itemtype="https://schema.org/FAQPage"> <div class="card table"> <table class="table"> <thead> <tr> <th><strong class="text-nowrap">Parameter</strong></th> <th><strong>Description and values</strong></th> </tr> </thead> <tbody> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>restartPeriod</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The period of time after which Make resets an organization's centicredits, operations, and data transfer.</p> <p><strong>Type:</strong> enum&lt;string&gt;</p> <p><strong>Values:</strong></p> <ul> <li>1 month</li> <li>1 year</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>operations</code> <span class="required">REQUIRED</span> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The number of operations that are available to scenarios in the organization. Operations reset after the restart period.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 0</li> <li><strong>max:</strong> 800000000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>transfer</code> <span class="required">REQUIRED</span> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The maximum amount of data transfer in bytes available to scenarios in the organization. Transfer resets after the restart period.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 104857600</li> <li><strong>max:</strong> 1099511627776</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>dslimit</code> <span class="required">REQUIRED</span> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The maximum number of data stores in the organization.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 1</li> <li><strong>max:</strong> 1000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>dsslimit</code> <span class="required">REQUIRED</span> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The maximum storage in bytes available across all data stores in the organization.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 1</li> <li><strong>max:</strong> 2306867200</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>interval</code> <span class="required">REQUIRED</span> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The minimum interval between two scheduled scenario executions in minutes. The interval setting is ignored when the scenario scheduling is set to "immediately".</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 1</li> <li><strong>max:</strong> 15</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>teams</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The maximum number of teams in the organization. Unlimited if not specified.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 1</li> <li><strong>max:</strong> 1000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>retention</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The number of days to store internal logs (<code>activity stream</code>, <code>userdata fulltext</code>, <code>userdata</code>, <code>debugdata</code>) for the organization. <br> The <code>retention</code> parameter limits for example the scenario execution detail storage duration. Scenario executions older than the <code>retention</code> period have only information about the scenario execution start and status.</p> <p><strong>Type:</strong> enum&lt;uinteger&gt;</p> <p><strong>Values:</strong></p> <ul> <li>7</li> <li>30</li> <li>60</li> <li><strong>default:</strong> 60</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>premiumApps</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Users in the organization have access to premium apps that have the same or lower premium tier as the value of the <code>premiumApps</code> parameter. <br> To check the installed apps premium tier: <br> 1. List all installed apps with the API call <code>GET /admin/apps</code> to get the app names in the <code>name</code> field. <br> 2. Run the API call <code>GET /admin/apps/{appName}</code>. Check the field <code>premiumTier</code> for the premium tier of the app.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 1</li> <li><strong>max:</strong> 10</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>priority</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the scenario execution priority of the scenarios in the organization. <br> Make executes scenarios from an execution queue. If there are scenarios scheduled to run at the same time, Make orders them for execution according to their priority.</p> <p><strong>Type:</strong> enum&lt;string&gt;</p> <p><strong>Values:</strong></p> <ul> <li>low</li> <li>medium</li> <li>high</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>allowOverage</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the percentage by which scenarios can exceed the number of available centicredits, operations, and data transfer. <br> For example, if the organization has the <code>operations</code> limit 1000 and the <code>allowOverage</code> parameter set to 120, the scenarios in the organization can use up to 1200 operations before Make stops and inactivates them.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 100</li> <li><strong>max:</strong> 200</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>apiLimit</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets a limit to the number of API calls per minute to work with the data contained in the organization. If a user is part of multiple organizations, Make limits API calls to each organization according to the organization's <code>apiLimit</code>. <br> <br> <div class="alert alert-warning">If you don't specify the <code>apiLimit</code>, Make sets the <code>apiLimit</code> to 0, which disables access to the data in the organization with the API.</div></p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 0</li> <li><strong>max:</strong> 2000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>fulltext</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows full text search in the scenario execution history to the users in the organization.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>dedicatedSso</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows logging in to the White Label platform with a custom single sign-on solution.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>installPublicApps</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows installation of apps that were created by user that is not part of the organization.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>creatingTemplates</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows the users to create scenario templates.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>scenarios</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the maximum number of active scenarios in the organization. The number is unlimited if not specified.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 1</li> <li><strong>max:</strong> 1000000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>dlqStorage</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the maximum storage in bytes for the scenario incomplete executions.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 1</li> <li><strong>max:</strong> 2097152000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>executionTime</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>The maximum duration of a scenario execution in minutes.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 5</li> <li><strong>max:</strong> 45</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>customVariables</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows using the <a href="https://www.make.com/en/help/functions/variables#custom-variables-1529751">custom variables</a> feature.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>customFunctions</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows using the <a href="https://www.make.com/en/help/functions/custom-functions">custom functions</a> feature.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>fslimit</code> <span class="required">REQUIRED</span> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Maximum individual file size in bytes that a scenario in the organization can transfer.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 5242880</li> <li><strong>max:</strong> 1048576000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>productManagement</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Defines the subscription management method. Organizations in the Make White Label platform must have this parameter set to "salesforce". You cannot change the value of this parameter.</p> <p><strong>Type:</strong> enum&lt;string&gt;</p> <p><strong>Values:</strong></p> <ul> <li>salesforce</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>iolimit</code> <span class="required">REQUIRED</span> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the maximum size of input and output webhook queues.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>min:</strong> 10</li> <li><strong>max:</strong> 10000</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>gracePeriod</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets a time limit in days during which the organization has access to all of its features without payment. Organizations in the Make White Label platform must have this parameter set to 0. You cannot change the value of this parameter.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li>0</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>appslimit</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the maximum number of apps used by all active scenarios in the organization. Unlimited if not specified.</p> <p><strong>Type:</strong> uinteger</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>onDemandScheduling</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows <a href="https://www.make.com/en/help/scenarios/scheduling-a-scenario#on-demand-scheduling-935240">scenario On-Demand scheduling</a>.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>scenarioIO</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Allows the <a href="https://www.make.com/en/help/scenarios/scenario-inputs">scenario inputs</a> feature for the scenarios in the organization.</p> <p><strong>Type:</strong> boolean</p> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>customProperties</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Enables the <a href="https://www.make.com/en/help/scenarios/custom-scenario-properties">custom properties</a> feature. With custom properties, your users can add custom metadata to scenarios and use them to sort and filter their scenarios. <br/> The specified number sets the maximum number of structure items in a custom property structure.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>default:</strong> 100</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>auditLogsDays</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Set the parameter to a non-zero number to enable the <a href="https://www.make.com/en/help/access-management/audit-logs">audit logs</a> feature. With audit logs, you can track and review user actions in Make. In addition, users with the "Owner," "Admin" and "Team Admin" roles can view audit logs in Make.<br/> The specified number is the amount of days for which Make stores the audit log entries. <br/> The default value 0 disables the feature.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>default:</strong> 0</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>webhookLogRetentionDays</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the number of days for which Make keeps webhook logs.</p> <p><strong>Type:</strong> uinteger</p> <p><strong>Values:</strong></p> <ul> <li><strong>default:</strong> 3</li> <li><strong>min:</strong> 3</li> <li><strong>max:</strong> 30</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>maxInterruptedExecutionDays</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Sets the maximum number of days a single scenario execution can stay interrupted before Make cancels it.</p> <p><strong>Type:</strong> enum&lt;uinteger&gt;</p> <p><strong>Values:</strong></p> <ul> <li>7</li> <li>30</li> <li>90</li> <li>365</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>dynamicDependencies</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Enables dynamic dependencies in a scenario. Dynamic dependencies allow users to map Make entities, like connections or data stores, in their scenarios.<br/> For example, <a href="https://www.make.com/en/help/connections/dynamic-connections">dynamic connections</a> are dynamic dependencies.</p> <p><strong>Type:</strong> boolean</p> <p><strong>Values:</strong></p> <ul> <li><strong>default:</strong> false</li> </ul> </td> </tr> <tr itemscope itemprop="mainEntity" itemtype="https://schema.org/Question"> <td> <p itemprop="name"> <code>dynamicConnections</code> </p> </td> <td itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer"> <div itemprop="text"> <p>Enables <a href="https://www.make.com/en/help/connections/dynamic-connections">dynamic connections</a> in a scenario. To allow using dynamic connections, you have to enable dynamic dependencies as well.</p> <p><strong>Type:</strong> boolean</p> <p><strong>Values:</strong></p> <ul> <li><strong>default:</strong> false</li> </ul> </td> </tr> </tbody> </table> </div> <!-- license input anchor end -->. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Assigns a universal discount to the organization. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Renames a connection of a custom SDK app. The new `name` must be a kebab-case slug and must be globally unique across all connections. Only private or published apps can be renamed; approved (public) apps are not eligible. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Renames a webhook of a custom SDK app. The new `name` must be a kebab-case slug and must be globally unique across all webhooks. Only private or published apps can be renamed; approved (public) apps are not eligible. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Creates a new team in the specified organization. You can set the team admin with the parameter `userTeamAdmin` in the request body. If you don't use the `userTeamAdmin` parameter and you are part of the organization, then Make sets you as the team admin. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Creates a new user. Specify the user's `name` and `email` in the request body. You have to either send an invitation mail to the user with the `sendEmail: true` or you have to specify the user password in the `password` field in the request body. If you send the invitation mail, the mail contains automatically generated password. The user has to change their password right after logging in. You can also set the user's country, locale and timezone with the request body parameters. If you don't specify the user's country, locale or timezone Make uses your account's country, locale or timezone. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Sets user role in the organization. Specify the user organization role ID in the request body. Get all available user role IDs and the corresponding user role names with the API call `GET /users/roles`. If the user is not a member of the organization, the API call adds the user to the organization with the specified role. If you add the user to the organization as "Admin" (`usersRoleId = 12`) and the organization has teams, Make assigns the user to the organization as the organization "Admin" and to all teams in the organization as "Team Admin". Once you add a user as "Team Admin" you cannot change their team role. The only option to change the "Team Admin" role is to remove the user from the team and re-add them with the specified team role. If you add the user to the organization with a role other than "Admin" Make doesn't add the user to any organization's teams. In the Administration interface, the user appears with the role "None" in all teams in the organization. The users with the role "None" in a team or an organization cannot access the team or organization data in any way. You cannot change the organization "Owner" with this endpoint. Use the API call to transfer organization ownership (https://www.make.com/en/api-documentation/organizations-organizationId-user-organization-roles-transfer-post) instead. To remove a user from an organization, send an empty request body. The API call removes the user with the specified `userId` from the organization, setting the user's organization role to "None". NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Transfer organization ownership to the user with the specified `userId`. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Sets the user role in the team. Specify the user team role ID in the request body. The user has to be already a member of the team's organization. Get all available user role IDs and the corresponding user role names with the API call `GET /users/roles`. If the user is not a member of the team, the API call adds the user to the team with the specified role. If you send an empty request body, the API call removes the user with the specified `userId` from the team, setting the user's team role to "None". NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Registers the user as a partner in the affiliate program.

Request a payout of available commissions.

Creates a new agent.

Create a new agent.

Run an agent with the provided ID.

Create a new context with an optional file upload.

Starts an interactive setup flow for a new AI Browser context (a managed `ai-browser-context` keychain key). Opens a fresh remote browser session where the user logs in to their services; the returned `liveViewUrl` is rendered in the Make UI. The flow is then driven with the returned `setupId`: poll its status, and complete or cancel it. The flow expires 15 minutes after it starts. Available only when the `is_ai_browser_contexts_enabled` feature flag is enabled.

Completes a browser context setup flow after the user has finished logging in. Releases the remote browser session, waits for the browser state to be written back into the context, and then — for a create flow — creates the `ai-browser-context` key, or — for a refresh flow — returns the existing key. A flow can be completed exactly once; only the user who started it can complete it. Available only when the `is_ai_browser_contexts_enabled` feature flag is enabled.

Starts an interactive refresh flow for an existing AI Browser context key. Opens a remote browser session attached to the key's existing context so the user can re-authenticate expired logins; the context (and the key) keep their identity. The flow is then driven with the returned `setupId`, exactly like a create flow. The flow expires 15 minutes after it starts. Available only when the `is_ai_browser_contexts_enabled` feature flag is enabled.

Proxies the error message and scenario blueprint to an AI-powered webhook that returns a human-readable explanation of what happened, why, and what to do next.

Creates a new connection with data passed in the request body. In the response, it returns all details of the created connection.

Restricts the connection's visibility to its access list (`visibility: locked`). The caller becomes the sole admin of the locked connection. Caller rule: only the connection's author can lock it, and that author must still be a member of the connection's team. A connection without an author cannot be locked. The operation is idempotent — locking an already locked connection succeeds without any change; the caller rule above still applies. Requires the *Locked connections* feature to be enabled for the organization.

Makes a locked connection visible to the whole team again (`visibility: team`) and clears the connection's entire access list. Only an admin of the locked connection can perform the flip. The connection's author is not changed. The operation is idempotent — flipping an already team-visible connection succeeds, provided the caller has the `account edit` permission; any residual entries on the connection's access list are still cleared. Requires the *Locked connections* feature to be enabled for the organization.

Verifies if a scope for a given connection is set. This endpoint returns the information if the connection is scoped (`true`) or not (`false`).

Updates the specified connection with data in the request body. Check which data you need to send to update the connection with the API call `GET /connections/{connectionId}/editable-data-schema`. The data might be different for each app and connection type. The new connection data replace the original connection data. Make sure to provide all relevant data. If a field is missing in the request body, Make replaces the field in the new connection with an empty value. For OAuth connections, you need to log in to Make and confirm the changes with the Reauthorize button. For the rest of the connection types, Make starts using the new connection data immediately. If the connection cannot be updated then the API call returns the error message "Cannot edit this connection." When this happens, create a new connection instead.

Verifies the connection status. This endpoint usually communicates with the API of the app that includes the given connection and verifies if credentials saved in Make are still valid. It returns the confirmation if the connection is verified (`true`) or not (`false`).

Creates a new Action for a Credential Creation. Either 'connection' or 'key' must be provided in the request body, but not both.

Declines a credential by setting its state to declined and recording the reason. This endpoint is idempotent and can be used to update the decline reason of an already declined credential.

Deletes a credential from the remote platform (Make Web API) and resets its state to pending. The credential can then be re-created through the normal creation flow.

Tests the OAuth connection and transitions to reauthorizing state if invalid. Returns an error if the connection is still valid.

Creates a new request for Credentials. Supports two flows: 1) Flow for new Make users, 2) Flow for existing Make users. DEPRECATED by Make; prefer the non-deprecated sibling.

Creates a new request for Credentials using app and module selections. Credentials (connections/keys) are automatically derived from the selected modules using the modules-with-credentials API. Supports two provider flows: 1. Existing Make user - Reference an existing Make user by their ID. The user will be added to the team if not already a member. 2. New user invitation - Invite a new user by providing their name and email.

Creates a custom properties structure. You can have only one custom properties structure for each combination of `associatedType`, `belongerType`and `belongerId` values. For example, you can create only one custom properties structure for scenarios in a specific organization. To create a structure for custom scenario properties, fill in the request body: - `associatedType`: `scenario` - `belongerType`: `organization` Check out the example API call. To define the custom properties structure items, use the API call to create custom properties structure item (./structure-items/post--custom-property-structures--custompropertystructureid--custom-property-structure-items.md).

Creates custom properties structure items. After creating a structure item, you cannot change its `name` and `type`. To add data to the custom properties, use the API call to fill in custom properties data (../../scenarios/custom-properties-data/post--scenarios--scenarioid--custom-properties.md).

Creates a new data store with data passed in the request body. In the response, it returns all details of the created data store.

Creates a new record in a data store with a given ID and returns all record details.

Creates a new data structure with data passed in the request body. In the response, it returns all details of the created data structure including its full specification.

Clones the specified data structure. Use the `targetTeamId` to clone the data structure to the specified team. The response contains all details of the data structure clone with data structure full specification.

Required scope: devices:write.

Triggers a retry of the specified incomplete execution. The incomplete execution runs with the blueprint from when the error happened. If you need to update the blueprint first, use the endpoint `PATCH /dlqs/{dlqId}`.

Triggers a retry of the specified incomplete executions. You can either use the `all` parameter to retry all incomplete executions of the scenario, or specify a list of incomplete execution IDs in the `ids` property. You can use the `exceptIds` parameter to exclude incomplete executions from retrying. The incomplete executions run with the blueprint from when the error happened. If you need to update the blueprint first, use the endpoint `PATCH /dlqs/{dlqId}`. Make puts the incomplete executions in a queue. If you are retrying a large number of incomplete executions, there might be a delay between receiving the response and Make retrying the incomplete execution.

Executes an App Endpoint (see `GET /imt/endpoints-usable` and the SDK Apps / Endpoints section for how Endpoints are defined) and returns its raw output. The response's `output` is currently a free-form, executor-defined value — its shape depends entirely on the executed Endpoint and is not constrained by this route.

Creates a custom function. Specify function `name`, `description` and `code` in the request body. You cannot use a JavaScript reserved word for the function `name`. Check the list of JavaScript reserved words (https://www.w3schools.com/js/js_reserved.asp). Make sure to use the same function name in the `name` field and in the function's `code`. Otherwise, you get the IM005 error. Make validates the custom function's code first. You get an IM005 error if the code validation fails. The validation might fail because of a syntax error in the function's code or when the code uses a JavaScript feature that Make doesn't support. Check the custom functions limitations (https://www.make.com/en/help/functions/custom-functions#limitations-of-custom-functions) in the Make Help center. Check availability of the custom functions feature with the API call `GET /organizations/{organizationId}` for the organization to which the team belongs. If the response contains `"customFunctions": true` pair in the `license` object then you have access to the custom functions feature. Refer to the Make pricing page (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

Checks the custom functions code. The response contains information whether Make validated the custom functions code successfully or whether there was an error. The code validation might fail because of an syntax error in the function's code or when the code uses a JavaScript feature that Make doesn't support. Check the custom functions limitations (https://www.make.com/en/help/functions/custom-functions#limitations-of-custom-functions) in the Make Help center. Check availability of the custom functions feature with the API call `GET /organizations/{organizationId}` for the organization to which the team belongs. If the response contains `"customFunctions": true` pair in the `license` object then you have access to the custom functions feature. Refer to the Make pricing page (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

Creates a new hook with data passed in the request body. In the response, it returns all details of the created hook.

Disables a hook with a given ID. Newly created hooks are enabled by default which means they are ready to accept data. The disabled hook does not accept any data. This endpoint can be useful when you want to debug the scenario functionality. In response, this endpoint returns the confirmation that the hook was successfully disabled.

Enables a disabled hook with a given ID. Newly created hooks are enabled by default which means they are ready to accept data. In response, this endpoint returns the confirmation that the hook was successfully enabled.

Starts the process of learning the request body structure by a hook with a given ID. When you send to the hook address a request with data in its body, you can use this endpoint to force the hook to start determining the payload data structure which will later be suggested in the scenario as the output of the hook. The data structure learning process also starts automatically when a new hook is created and stops once the data structure is determined. If you want to stop this process, you can use the Learn stop (./post--hooks--hookid--learn-stop.md) endpoint.

Stops the process of learning the request body structure by a hook with a given ID. When you send to the hook address a request with data in its body, you can use the Learn start (./post--hooks--hookid--learn-start.md) endpoint to force the hook to start determining the payload data structure which will later be suggested in the scenario as the output of the hook. The data structure learning process also starts automatically when a new hook is created and stops once the data structure is determined. You can use this endpoint to stop the learning process at any time.

Sets data for a hook with a given ID. Data differ depending on the hook type. It returns the confirmation if the hook data was changed (`true`) or not (`false`).

Returns the save-time locked-entity verdict for a blueprint the caller is about to execute: rejects with `IM002` when a module places a locked connection or key the user may not use and that placement is not already stored unchanged. Only services that gate a manual execution on this verdict may call it — any other caller is rejected with `SC500`, since reaching this route is an integration bug rather than a client-facing access denial. Fail-closed: when the verdict cannot be reached, the response is an `IM016` error, never an allow. While the organization's enforcement flag is off (log-only rollout), a violation is logged and the response is an allow — the same softening the save hooks apply; `IM016` stays fail-closed in both modes. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Deletes a hook using ISC authorization, forcing removal and confirming the operation on behalf of the caller. Only the Executor may call this endpoint — any other caller is rejected with `SC500`, since reaching this route is an integration bug rather than a client-facing access denial. Note: the underlying procedure does not check hook existence up front — an unknown `hookId` fails with `IM002` (its permission check runs against a null team) rather than a dedicated not-found error. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Registers a new hook (webhook/mailhook) for a team using ISC authorization. Only the Executor may call this endpoint — any other caller is rejected with `SC500`, since reaching this route is an integration bug rather than a client-facing access denial. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Creates a new team connection (TAC) for the specified team. Non-OAuth connections are automatically tested after creation via the ConnectionWorker validate/test lifecycle — on success the connection is marked as valid and credentials are persisted. If the test fails, the connection is deleted and a 422 is returned. OAuth connections are created but left unauthorized — the caller must complete the OAuth flow separately. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Creates a key in your keychain. Use the list of key types (./get--keys--types.md) API call to get a list of available key types for the `typeName` parameter. Specify additional parameters in the `parameters` object based on the key type.

Restricts the key's visibility to its access list (`visibility: locked`). The caller becomes the sole admin of the locked key. Caller rule: only the key's author can lock it, and that author must still be a member of the key's team. A key without an author cannot be locked. The operation is idempotent — locking an already locked key succeeds without any change; the caller rule above still applies. Requires the *Locked connections* feature to be enabled for the organization.

Makes a locked key visible to the whole team again (`visibility: team`) and clears the key's entire access list. Only an admin of the locked key can perform the flip. The key's author is not changed. The operation is idempotent — flipping an already team-visible key succeeds, provided the caller has the `key edit` permission; any residual entries on the key's access list are still cleared. Requires the *Locked connections* feature to be enabled for the organization.

Marks all notifications as read and returns the IDs of the updated notifications in the response.

Authorize (deprecated). DEPRECATED by Make; prefer the non-deprecated sibling.

Oauth Callback (deprecated). DEPRECATED by Make; prefer the non-deprecated sibling.

Oauth Callback Id (deprecated). DEPRECATED by Make; prefer the non-deprecated sibling.

Parses saml xml to json with info about user.

Extend (deprecated). DEPRECATED by Make; prefer the non-deprecated sibling.

Reauthorize (deprecated). DEPRECATED by Make; prefer the non-deprecated sibling.

Create a new organization using the data sent in the request body. Successful response contains all information about the created organization.

Accept invitation.

Verify the domain for given organization using DNS TXT record method.

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}`.

A successful response contains information about the new organization and user. The endpoint requires `regionId` and `countryId` in the request body. The `regionId` can be retrieved from the GET `/enums/imt-regions` endpoint, and the `countryId` can be found in GET `/enums/countries`. The `operations` parameter must be a multiple of 10000. The user name can be an existing user or an external contact without a Make account yet. Refer to the MMS page (https://help.make.com/make-managed-services-mms) for Make Managed Services (MMS) overview.

Searches the module input/output (IO) data produced by a single scenario execution using a free-text `query`, and returns every matching IO-data record for that execution — no grouping and no pagination. The scenario's team is resolved from `scenarioId`; the caller must hold the scenario-logs read permission on that team. The `from` and `to` bounds are applied at UTC-day granularity — only the calendar-day portion of each timestamp is honored. When omitted, the search defaults to the last 7 UTC days, so supply a window that covers the execution's timestamp to search older executions.

Counts how many scenarios and executions across the organization (or a specific team) produced module input/output (IO) data matching a free-text `query`. Returns global, exact totals plus a per-scenario breakdown of how many distinct executions matched. Counts are computed over the entire match set (not a page): there is no client-facing pagination. Internally the endpoint pages through all matching `(scenario, execution)` pairs using an Elasticsearch composite aggregation. The `from` and `to` bounds are applied at UTC-day granularity — only the calendar-day portion of each timestamp is honored. When omitted, the search defaults to the last 7 days, mirroring the other organization scenario-log endpoints.

Searches the module input/output (IO) data produced by scenario executions across the organization (or a specific team) using a free-text `query`. Matches are grouped by execution: each result contains up to 5 IO-data records that matched the query together with the metadata of the parent execution. Use the optional filters to restrict the search to specific teams, scenarios, apps, modules, or a time window. The `from` and `to` bounds are applied at UTC-day granularity — only the calendar-day portion of each timestamp is honored. IO-data records earlier or later within the same UTC day as a supplied bound may still appear in the results, and the execution metadata attached to each match may include executions from the immediately adjacent UTC days.

For a single scenario, counts how many distinct executions produced module input/output (IO) data matching a free-text `query`. The `from` and `to` bounds are applied at UTC-day granularity — only the calendar-day portion of each timestamp is honored. When omitted, the search defaults to the last 7 days.

Retrieves execution logs across all scenarios in an organization (or a specific team within the organization), narrowed by `from`/`to`, execution `status`, `scenarioIds`, or a substring of the `errorMessage`. When `from` or `to` are omitted, the time window defaults to the last 7 days. Results are returned in reverse-chronological order. The `from` and `to` bounds are applied at UTC-day granularity — only the calendar-day portion of each timestamp is honored. Executions that occurred earlier or later within the same UTC day as a supplied bound may still appear in the results.

Create a new subscription.

Sets Free plan subscription.

Schedules a pause for the active monthly self-service subscription. The pause becomes effective at the end of the current paid period and is automatically resumed on `resumeAt`. While paused the organization is treated as unlicensed (0 credits) and Stripe collection is suspended.

Ends the pause for the subscription. If the pause is still scheduled (current period not yet ended) it is simply cancelled — no charge, no billing reset. If the pause is in effect, the subscription is resumed immediately, billing anchor is reset to now and a fresh period is charged.

Advance a test clock (TEST ONLY).

Trigger a pause/unpause task for an specific organization (TEST ONLY).

Claims a cancellation offer discount for the organization. The user must have the 'payment edit' permission on the organization. The organization must be eligible (no existing universal discount, no active coupon/promo).

Activates a dormant universal discount on the user's current subscription. The current price must be eligible and no other discount can be active.

Transfer organization ownership to the specified user.

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 Make pricing page (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

Registers a new outbound webhook subscription for the organization. The response includes a one-time `signingSecret` that is not retrievable later. Endpoint is proxy for the Outbound Webhooks service. Full schema documentation is available at https://github.com/integromat/outbound-webhooks/blob/master/openapi/openapi.json.

Call RPC.

Creates a new team label. Requires `scenario edit` on the team. Label names are unique (case-insensitive) within a team.

Assigns every accepted team label to every accepted scenario in one transaction. The raw request accepts up to 100 label IDs and 1,000 scenario IDs before duplicate IDs are removed. Missing, non-team, and different-team labels are rejected with the same `IM013` response. Missing and different-team scenarios are rejected with `IM002`; trashed scenarios in the requested team are rejected with `IM301`. Existing assignments are accepted no-ops. A processed request returns `200` even when every resource is rejected.

Assigns a team label to a single scenario. A team label may only be applied to scenarios in that same team. Idempotent.

Removes every accepted team label from every accepted scenario in one transaction. The raw request accepts up to 100 label IDs and 1,000 scenario IDs before duplicate IDs are removed. Missing, non-team, and different-team labels are rejected with the same `IM013` response. Missing and different-team scenarios are rejected with `IM002`; trashed scenarios in the requested team are rejected with `IM301`. Absent assignments are accepted no-ops. A processed request returns `200` even when every resource is rejected.

Creates a new scenario with data passed in the request body. In the response, it returns the details of the created scenario. The blueprint is not returned; retrieve it separately via the Get scenario blueprint endpoint.

Adds new buildtime team or user defined variable/s. Buildtime variables should be prefixed either with a `TAC_` (for team defined variables) or with a `PAC_` (for personal user defined variables), followed by the connection value. If a variable already exists, an error will be thrown. If a variable's name is not within scenario input specification, an error will be thrown. If the adding of new variables was successful the reponse would be `OK`.

Clones the specified scenario. The response contains all information about the scenario clone. You have to know which app integrations the scenario contains. You can get a list of apps used in the scenario with the API call `GET /scenarios/{scenarioId}` in the `usedPackages` array. If you are cloning the scenario to a different team and the scenario contains an app module, webhook or data store, you have to either: - map the entity ID to a different entity with the correct properties. For example, you can map an app module connection to a different connection of the same app with the same scopes, or - use the `notAnalyze` query parameter to turn off the scenario clone blueprint analysis. When you turn off the scenario blueprint analysis you can map the entity ID to the `null` value, which omits the entity settings. The scenario blueprint analysis makes sure that the scenario clone will work without further changes. If you turn off the scenario blueprint analysis, check the configuration of all entities in the scenario clone. If you are cloning the scenario to a different team and the scenario contains a custom app or a custom function, which is not available for the users in the team, use the `confirmed` query parameter to confirm cloning of the scenario. Otherwise, you get an error listing the custom function that you have to create in the team. Refer to the request body parameters description and examples for more information.

Fills in custom properties data for the specified scenario. The scenario has to have no custom properties data. The data you fill in has to conform to the current custom scenario properties structure. You have to specify a value for every required item, otherwise you get an error. To update existing data, use the following API calls: - Update custom properties data (./patch--scenarios--scenarioid--custom-properties.md) - Set custom properties data (./put--scenarios--scenarioid--custom-properties.md).

Stops a running execution. Use `force: true` to immediately terminate the execution without waiting for the current module to finish.

Creates a new scenario note with data passed in the request body. As the response, it returns all details of the created scenario note.

This endpoint is set to internal because the scenario drafts feature is available only on the Celonis platform. In Make, this endpoint has no functionality. Original description: Publishes a draft of a scenario with a given ID. In the response, it returns all details of the published scenario.

Replays the specified scenario execution. The scenario has to be active.

Restores a soft-deleted ("trashed") scenario with the given ID back to active, as long as it is still within the 30-day recovery window. The scenario's runnable state (apps, connections, modules, webhook wiring) is re-derived best-effort from its surviving blueprint; if the blueprint references something deleted while the scenario sat in trash, the restore still succeeds and the scenario is flagged with `containsErrors` so it can be fixed by editing. Locked connections and keys the restoring user is not allowed to use are cleared from the restored blueprint rather than blocking the restore: those modules come back with no connection selected, and the scenario is flagged with `containsErrors` because it cannot run until someone selects one. Every module cleared this way is listed in `strippedModules` so the caller can tell the user which modules need a new connection; the list is empty when nothing was cleared. Requires the `scenario edit` permission. Only a scenario that is currently in trash can be restored — an already-active one is rejected with 404, as is a scenario beyond the 30-day window.

Runs the specified scenario. The scenario has to be active. If your scenario has required scenario inputs you have to provide the scenario inputs in the request body. If the scenario provides scenario outputs, these are returned in the response. The scenario is not run when its organization or team is paused because an operations or data transfer limit was exceeded. In that case the call returns `429` with the code `IM310`, the same way Make stops scheduling the organization's scenarios. Note: Organization request limits (https://developers.make.com/api-documentation/getting-started/rate-limiting) do not apply for this endpoint.

Activates the specified scenario. Also runs the scenario if the scenario is scheduled to run at regular intervals. Read more about scenario scheduling (https://www.make.com/en/help/scenarios/scheduling-a-scenario). The API call response contains the scenario ID and the scenario `isActive` property set to `true`.

Deactivates and stops the specified scenario if the scenario is running. The API call response contains the scenario ID and the scenario `isActive` property set to `false`.

Creates a new scenario folder with data passed in the request body. As the response, it returns all details of the created scenario folder.

Moves selected scenarios from the specified team into a target folder. Use `targetFolderId: null` to uncategorize them.

Sets manual positions for direct sibling folders within one parent. Omitted siblings have their position cleared and are listed alphabetically after positioned folders.

Retrieves an array of scenarios containing aggregated list of operations, dataTransfer and centicredits per module within a specified time period.

Creates a share of the specified scenario.

Creates a new tool with data passed in the request body. In the response, it returns all details of the created scenario including its blueprint.

Creates a new app with data passed in the request body. In the response, it returns all details of the created app.

Leaves the current phase without submitting: `preparing` returns to `dormant` (the draft is kept, so the answers can be restored later), and a submission that is still in review is withdrawn back to editing (`review` → `preparing` — the UI's "Edit submission"). Fails with `409` in any other phase. Only the app's author (or an administrator) may do this. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

Moves the review from `dormant` to `preparing` and opens the form for editing. On the first new-flow contact with an app that has legacy review data, the draft is seeded best-effort from the legacy review form (API docs link, test scenarios, error-handling scenario). Fails with `409` in any other phase. Only the app's author (or an administrator) may do this. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

Submits the prepared form: the review moves from `preparing` to `review` and enters the automatic step (`reviewStep: auto`). The current draft is snapshotted into `submittedForm` — later draft edits do not change the submitted record. Completeness of the form is the client's responsibility (the readiness gate); the server does not re-validate it. Fails with `409` in any other phase. Only the app's author (or an administrator) may submit. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

Set app base configuration.

Set App Visibility.

Clone App.

Clones the app to the next major version with the same app name. Requires the "allow_apps" feature flag to be enabled.

Set App ClosedSource.

Commit Changes.

Creates a new endpoint on the app version. The endpoint starts private and unapproved. By default (`endpointInitMode: example`) its sections (`api`, `inputParameters`, `outputParameters`) and `context` are seeded from a built-in endpoint template; pass `endpointInitMode: blank` to start with empty sections instead. Which template seeds an `example` endpoint is chosen with `templateType`: `regular` (default) is a single-route example, while `universal` is an arbitrary-call example that forwards a caller-supplied method, path, query string, headers and body to the app's API — a `universal` endpoint is additionally created with the `arbitraryCallHint` annotation set. All sections can be edited afterwards via the section endpoints. The `name` must be alphanumeric, start with a letter, be 3 to 128 characters long, unique within the app version, and not a reserved keyword. `attachedAccounts` is optional; every connection it lists must belong to the app, otherwise the request is rejected.

Archives or unarchives an endpoint. Archiving is a zone-only flag (never synced to HQ) used to hide endpoints that can no longer be deleted (e.g. on public apps). A public (visible) endpoint cannot be archived — set it private first. Use the path segment `archive` or `unarchive`.

Marks an endpoint as deprecated or removes the deprecation. Deprecation is a soft flag that can be reflected in the UI. Use the path segment `deprecate` or `undeprecate`. DEPRECATED by Make; prefer the non-deprecated sibling.

Sets an endpoint public or private. Only public endpoints are compiled into the app's manifest. Use the path segment `public` or `private`.

Creates a copy of an existing endpoint under a new name within the same app version. All sections and metadata are copied; the clone always starts private and unapproved. The `newName` must be alphanumeric, start with a letter, be 3 to 128 characters long, and be unique within the app version.

Adds a connection (account) to the endpoint's list of attached connections. The connection must belong to the app, otherwise the request is rejected.

Create Function.

Binds the app version to a GitHub repository through a Make GitHub connection. When the repository does not exist yet under the connection's GitHub user, a clean private repository is created (initialized with GitHub's default README only — no app source is pushed; content sync is a separate flow). GitHub's response is authoritative for the stored `owner`, `repoUrl`, `defaultBranch` and `private` values — the optional request fields of the same names are hints only. Re-binding the same `(connection, owner/repo, branch)` combination updates the existing binding instead of failing. Requires a connection whose provider is GitHub, otherwise responds with `400`. Only the app's author (or an administrator) may create bindings.

Applies the latest commit on the bound branch to the app version. Files whose content differs from the local state are written through the same edit path the SDK editor uses — directly to the component tables on editable apps, or as pending changes (`apps.change`) on approved public apps. Sub-entities that exist only in the repository are created first: modules, RPCs and functions are created under their repository folder names, while connections and webhooks are re-identified by the `$id` in their `metadata.json` (matching the entity's stable external ID) and created with auto-generated names when unknown — this is what makes one repository cloneable into multiple apps. Files that fail to apply (e.g. invalid JSONC) are skipped individually; the rest of the pull proceeds. When the remote HEAD equals the last synced commit the call is a cheap no-op that leaves the stored checksum snapshot untouched (so unpushed local drift stays visible in the diff); a snapshot is only seeded from the local state when the binding does not carry a file-format snapshot yet. On success the binding's sync state (`lastPulledAt`, `lastPulledCommitSha`, `syncStatus`, checksum snapshot, `nameMap`) is updated and returned. Only the app's author (or an administrator) may pull.

Commits the app version's complete source tree (app sections, readme, icons, modules, RPCs, functions, webhooks, connections) to the bound repository branch as a single commit, using the binding's Make connection for authentication. When the bound repository does not exist yet it is created as a private repository under the connection's GitHub user and initialised with a bootstrap tree. Connection and webhook folders are committed under stable per-binding folder names (`nameMap`) so the repository layout survives renames; each of their `metadata.json` files carries a stable `$id` used to re-identify the entity on later pulls. On success the binding's sync state (`lastPushedAt`, `lastPushedCommitSha`, `syncStatus`, per-file checksum snapshot) is updated and returned. On failure the binding is marked with `syncStatus: error` and `lastError`. Only the app's author (or an administrator) may push.

Create Module.

Set Module Archive Status.

Set Module Deprecation.

Set Module Visibility.

Creates a duplicate of a module.<br />.

beta, stable<br />.

Request Review.

Rollback Changes.

Create RPC.

Tests the RPC<br />.

Uninstall App from Organization.

Create Connection.

Create Webhook.

Recreates an existing app connection and synchronises it with HQ.

Accept App Invite.

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

Checks if every given e-mail is an active member of the team. Evaluates to false if any of the input e-mails are not part of the team. This endpoint uses JWT authorization. Please note that JWT authorization is not available in our open API, use tools like Postman for testing.

Adds a user to a connection's access list (entity ACL) with a role. Requires `entity manage` on the connection, and the target user must already be a member of the connection's team. Returns `409` when the user is already on the access list and `400` when they are not a team member or the feature is disabled.

Adds a user to a key's access list (entity ACL) with a role. Requires `entity manage` on the key, and the target user must already be a member of the key's team. Returns `409` when the user is already on the access list and `400` when they are not a team member or the feature is disabled.

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 (https://www.make.com/en/help/general/pricing-parameters) for Make pricing plans overview.

Creates a new template with data passed in the request body. In the response, it returns all details of the created template.

Publishes a private template with a given ID. In the response, it returns all details of the template.

Requests approval of the published template with the given IDs of its private and published versions. In the response, it returns all details of the template.

Updates the specified user role in the organization. Only organization owners and admins can change the user organization roles. Refer to the Make Help center for a breakdown of the user role permissions (https://www.make.com/en/help/access-management/organizations#organization-roles). Specify the ID of the new role for the user in the request body. Get all available user role IDs and the corresponding user role names with the API call `GET /users/roles`. You cannot change the organization "Owner" with this endpoint. Use the API call to transfer organization ownership (./post--users--userid--user-organization-roles--organizationid--transfer.md) instead. If you send an empty request body, the user with the specified `userId` will be removed from the organization.

Transfer organization ownership to the user with the specified `userId`. Only organization owner can transfer their ownership to another user.

Updates the user role in the team with the specified `teamId`. Get the mapping of the `userRoleId` and the user role `name` with the API call `GET /users/roles`.

Creates a new custom organization or team role. Requires the `organization custom roles edit` permission on the organization.

Submits the onboarding survey response for the authenticated user. Optionally pins preferred apps for the user in their organization.

Pins an app for the authenticated user within the specified organization. Accepts both SDK apps (`appName` prefixed with `app#`) and native apps (bare package name). Pins are version-agnostic — the UI always renders the latest available version. Pinning is idempotent — pinning an already-pinned app is a no-op (no error). The app must exist in the catalog; otherwise a 404 is returned.

Pins a module under the specified `appName` for the current user in the specified organization. Pins are version-agnostic — the UI always renders the latest available version. The module must belong to the app; otherwise a 404 is returned. Idempotent — pinning an already-pinned module is a no-op.

Updates the UI settings of the user.

Removes up to 100 users from an organization in one request. This is the bulk counterpart of `POST /users/{userId}/user-organization-roles/{organizationId}`. List the target users in the request body `userIds` array (duplicates are ignored). Only removal is supported for now: `usersRoleId` must be `null` or omitted. Bulk role assignment is planned but not yet available — sending a non-null `usersRoleId` is rejected with HTTP 400. Only organization owners and admins (permission `organization user add and edit`) can call this endpoint. The operation is all-or-none: it is applied only when every listed user is eligible. If any user is ineligible, nothing is changed and the call fails with `IM019` (HTTP 400) whose response reports every failing user (`userId`, `name`, error `code` and `message`). Removing users that authored connections used by active scenarios, or that own a non-empty private space, needs confirmation. An unconfirmed request that would trigger such side effects fails with `IM004` (HTTP 406) and a payload describing them; re-send with `confirmed=true` (and `deleteConnections` set as desired) to proceed. Available on app zones only.

Replaces the category taxonomy of the new SDK app review form with the posted list. The catalog's source of truth is external (maintained outside Make and pushed here by a sync script), so this endpoint takes the whole list and merges it — it is not a per-category create/update: * an entry whose `slug` is new is created; * an entry whose `slug` already exists has its `name` and display order updated; * an entry whose `slug` was retired by an earlier sync is brought back; * a category or subcategory the list no longer contains is retired — it stops being offered by the form, but is not deleted, so a slug already stored in a review form keeps resolving to its label. A later sync that lists it again revives the same row. Display order is the order of the array (and, for subcategories, of each `subcategories` array). `slug` is optional: when omitted it is derived from the label (diacritics stripped, lowercased, runs of non-alphanumerics collapsed to a dash, so `"Microsoft (Enterprise)"` → `microsoft-enterprise`). Pin an explicit `slug` whenever the label may be reworded later — the slug is the identity stored in review forms, so letting it follow a rename retires the old value and creates a new one instead of relabelling in place. A label with no ASCII alphanumerics at all (e.g. CJK-only) cannot be derived from and is rejected with `400` (IM005); pass a `slug` for it. The operation is idempotent: re-posting an unchanged list reports no changes and sends nothing anywhere, which makes it safe to run on a schedule. An empty array is rejected rather than treated as "retire everything" — that payload is almost always a syncing script whose upstream fetch came back empty. The catalog is platform-global and HQ-mastered. On a multi-zone (HQ-managed) installation the zone that accepts this request computes the diff between the posted list and its catalog and hands the diff to HQ; nothing is applied locally by the request itself. HQ applies the diff to the master copy and broadcasts it to every zone — including this one, which is how the local catalog converges, typically within a second. A read issued immediately after this call may therefore still serve the previous catalog. When HQ cannot be reached the request fails with `503` and nothing was changed anywhere — simply retry. On a single-instance (master mode) installation there is no HQ and the diff is applied locally within the request. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903). NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Edit one system setting. NOT CALLABLE with this connection's API token: every /admin route answers 403 "VPN access only" to any customer; it is on Make's internal network.

Updates a data store record with a given key by passing new data in the request body. It replaces the entire resource with the new values. In the response, this endpoint returns all details of the updated data.

Updates the stored data and/or associated key ids of a hook using ISC authorization. Only the Executor may call this endpoint — any other caller is rejected with `SC500`, since reaching this route is an integration bug rather than a client-facing access denial. Note: the underlying procedure does not check hook existence up front — an unknown `hookId` fails with `IM002` (its permission check runs against a null team) rather than a dedicated not-found error. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Updates the external account id associated with a hook using ISC authorization. Passing `null` clears the external account id. Only the Executor may call this endpoint — any other caller is rejected with `SC500`, since reaching this route is an integration bug rather than a client-facing access denial. Note: the underlying procedure does not check hook existence up front — an unknown `hookId` fails with `IM002` (its permission check runs against a null team) rather than a dedicated not-found error. NOT CALLABLE with this connection's API token: the /internal plane is not served on the public API host.

Updates team or user defined buildtime variable/s. The endpoint updates and overwrites exsiting records with the newly provided values, meaning any existing buildtime variable which is not provided through the payload will be overwritten. Buildtime variables should be prefixed either with a `TAC_` (for team defined variables) or with a `PAC_` (for personal user defined variables), followed by the connection value. If a variable doesn't exist, it will be added provided that its name is within the scenario input specification. If the updating of variables was successful the reponse would be `OK`.

Sets custom properties data for the specified scenario. Make replaces the original data with the data you send in the request body. You have to specify a value for every required custom properties structure item, otherwise you get an error. The scenario has to have custom property data already. The new data set has to conform to the current custom scenario properties structure. If the initial data is empty, then the API call returns an error. To fill in first values to the custom properties, use the API call to fill in custom properties data (./post--scenarios--scenarioid--custom-properties.md).

Why the docs are internal: It's not clear how to use this EP. The example suggest that the EP can only change the trigger epoch. But the EP's SQL routine and original documentation suggest that the EP is supposed to update any module. I wasn't able to reproduce that use case even with the simplest modules. Furthermore, the EP always returns successful response, even though it didn't update anything. This causes a lot of confusion and frustration ot the users. So until the usage of the EP is clear the docs should be hidden. 2023-06-06, agreed with Ondrej Vesely. Original docs: Sets the module data for a scenario with a given ID by passing new values in the request body. It replaces the entire resource with the new values. In the response, it returns the confirmation if the scenario was updated.

Saves a scenario recovery snapshot for a given scenario and removes the present one if it exists. scenarioId = 0 is a sentinel for unsaved draft scenarios (no ownership check required). Uses team-scoped storage for cross-team draft isolation.

Overwrites the auto-saved draft of the review form. The whole draft is replaced with the request body, so send the complete current form value on every save (the client auto-saves it debounced). Allowed only while the phase is `preparing` — in any other phase the call fails with `409`. Completeness is not validated here; the client's readiness gate decides when the form can be submitted. Only the app's author (or an administrator) may edit the draft. Available only while the `is_sdk_app_review_enabled` feature flag is on, otherwise responds with `400` (IM903).

Sets the common data for the app based on the parameters passed in the request body. In the response, it returns all details of common data. Common data usually contain sensitive information like API keys or API secrets and these details are shared across all modules.

Writes one endpoint section. The `api` section accepts an object or an array of objects; `scope`, `inputParameters` and `outputParameters` accept an array. On an approved app the write is recorded as a pending change (returned as `change`) instead of being applied immediately.

Sets the centicredits cost formula and its descriptive fields for an endpoint. Requires the `allow_apps_set_consumable` user feature. Omitted fields are cleared (set to null).

Available sections: base, groups, install, installSpec<br />.

Available sections: base, groups, install, installSpec<br />.

Available sections: api, epoch, parameters, expect, interface, samples, scope<br />.

Set Module Consumable.

Available sections: api, epoch, parameters, expect, interface, samples, scope<br />.

Available sections: api, epoch, parameters, expect, interface, samples, scope<br />.

Available sections: api, epoch, parameters, expect, interface, samples, scope<br />.

Available sections: api, epoch, parameters, expect, interface, samples, scope<br />.

Available sections: api, epoch, parameters, expect, interface, samples, scope<br />.

Set App Docs.

Submit App Review Form.

Available sections: api, parameters<br />.

Available sections: api, parameters, scopes, scope, installSpec, install<br />.

Set Connection Common.

Set Webhook Section.

Updates an email for a user with a given ID by passing new data in the request body. It replaces the entire resource with the new values. In the response, it returns the confirmation if the email was changed.

Updates the authenticated user's notification settings for the team and notification type specified by the `teamId` and `notificationId`. Get the mapping of the `notificationId` and the team notification setting type with the API call `GET /enums/user-email-notifications`. Note that you can only update notification settings for the user associated with the API key used for authentication. Some notification types require a specific team permission. Enabling such a type for a user who does not hold the required permission fails with `403`. Disabling a notification type is always allowed, regardless of permissions or feature flags.