Everything an AI agent can do with the Make API.

A reference guide for building AI agents: every method, how to authenticate, and the permissions each one needs.

Endpoints47
API versionv2
Last updated23 June 2026
Orientation

How the Make API works.

The Make API is how an app or AI agent works with a Make organization: listing and running scenarios, reading their execution logs, managing the connections to outside apps, and reading and writing records in data stores. Access is granted through an API token whose scopes are chosen when the token is made, and an agent is limited to the organizations and teams that token can reach. Make also runs a hosted server an agent can call through the Model Context Protocol, which turns scenarios into callable tools.

47Endpoints
9Capability groups
22Read
25Write
16Permissions
Authentication
Every call needs a token, sent as 'Authorization: Token '. The token is a user authentication token created in the Make profile, and its scopes are picked at creation time. OAuth 2.0 is also offered for apps acting on behalf of a user, with the authorization code flow, refresh tokens for confidential clients, and PKCE for public clients. A token can only reach the organizations and teams its user is a member of.
Permissions
Make uses granular scopes, each a short token in the form area:access, such as scenarios:read, scenarios:write, scenarios:run, connections:read, connections:write, datastores:read, datastores:write, hooks:read, hooks:write, teams:read, organizations:read, templates:read, and user:read. Scopes are selected when the token is created, so a token carries only the access it was granted. Running a scenario needs scenarios:run alongside read and write, and creating an organization needs admin:write.
Region hosts
The API answers on a region host, not a single global domain. The base URL is https://{zone}.make.com/api/v2, where {zone} is the zone an organization lives in, such as eu1, eu2, us1, or us2. A call must go to the zone that holds the organization, and the zone shows in the URL of the Make web app.
Data model
The API is resource-oriented JSON over HTTPS. The main resources are scenarios, their executions and logs, connections to outside apps, data stores and the records inside them, hooks, and the account-level teams, organizations, users, and templates. Most endpoints require a paid plan, and the org-scoped list endpoints take a teamId or organizationId to say which account to read.
Connect & authenticate

Connection & authentication methods.

How an app or AI agent connects to Make determines what it can reach. There are several routes, each governed by the token behind it and the scopes that token carries.

Ways to connect

REST API (v2)

The REST API answers at https://{zone}.make.com/api/v2, where the zone is the region the organization lives in, such as eu1, eu2, us1, or us2. It is resource-oriented JSON over HTTPS, and a call must go to the zone that holds the target organization.

Best forConnecting an app or AI agent to Make.
Governed byThe API token and the scopes it carries.
Docs ↗

MCP server (Model Context Protocol)

Make hosts its own Model Context Protocol server, which turns active and on-demand scenarios into tools an agent can run and can manage connections, hooks, and data stores. It connects over streamable HTTP or server-sent events at mcp.make.com using OAuth, or at a zone host with an MCP token. It is generally available, with scenario-running on all plans and management tools on paid plans.

Best forConnecting an app or AI agent to Make through the Model Context Protocol.
Governed byOAuth or an MCP token, and the access of the user behind it.
Docs ↗

Hooks (inbound triggers)

Hooks are inbound triggers. A hook receives an HTTP request or an email from an outside service and starts a scenario. The hooks endpoints list, create, and manage those triggers; they do not register a receiver for Make's own events.

Best forStarting a Make scenario from an outside event.
Governed byThe API token and the hooks:read or hooks:write scope.
Docs ↗
Authentication

API token

A user authentication token created in the Make profile, sent as 'Authorization: Token '. Its scopes are chosen when the token is created, so the token carries only the access it was granted, and it reaches only the organizations and teams its user belongs to.

TokenUser authentication token
Best forServer-side automation and AI agents
Docs ↗

OAuth 2.0

OAuth 2.0 lets an app act on behalf of a Make user. It uses the authorization code flow, with refresh tokens for confidential clients that can keep a secret, and PKCE for public clients such as single-page and mobile apps. The client is registered with Make's authorization server first.

TokenOAuth access token
Best forApps acting on behalf of a user
Docs ↗
Capability map

What an AI agent can do in Make.

The Make API is split into areas an agent can act on, such as scenarios, connections, data stores, and hooks. Each area has its own methods and its own scopes, and some grant access to far more than others.

Scenarios

10 endpoints

List, read, create, update, clone, and delete scenarios, and start, stop, or run them.

Writes here change real scenario data, and running a scenario performs its actions for real.
View endpoints

Executions & logs

3 endpoints

List a scenario's run logs and read the details of a single execution.

These are read-only views of past runs.
View endpoints

Connections

6 endpoints

List, read, create, rename, and delete the connections to outside apps, and verify a connection.

Writes here change the credentials scenarios use to reach outside apps.
View endpoints

Data stores

8 endpoints

List, create, update, and delete data stores, and read, write, and delete the records inside them.

Writes here change stored records, and a bulk delete can clear a whole store.
View endpoints

Hooks (triggers)

8 endpoints

List, create, update, and delete inbound hooks, and enable, disable, or ping them.

Writes here change the triggers that start scenarios from outside events.
View endpoints

Teams

3 endpoints

List the teams in an organization, read a team, and create a team.

Writes here change real team data.
View endpoints

Organizations

3 endpoints

List organizations, read an organization, and create an organization.

Writes here change real organization data, including billing-adjacent settings.
View endpoints

Users

2 endpoints

List the users in an organization or team, and find users by permission.

Writes here change real user accounts.
View endpoints

Templates

4 endpoints

List templates, read a template, read its blueprint, and create a template.

Writes here change real template data.
View endpoints
Endpoint reference

Every Make API method.

Filter by method, access, or permission, or search any path. Select a row for version detail, rate limits, the related webhook event, and the source.

MethodEndpointWhat it doesAccessPermissionVersion

Scenarios

List, read, create, update, clone, and delete scenarios, and start, stop, or run them.10

Takes a teamId or organizationId query parameter to say which account to list.

Acts onscenario
Permission (capability)scenarios:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onscenario
Permission (capability)scenarios:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onscenario
Permission (capability)scenarios:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onscenario
Permission (capability)scenarios:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onscenario
Permission (capability)scenarios:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onscenario
Permission (capability)scenarios:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Activating sets the scenario live; it does not run it once on its own.

Acts onscenario
Permission (capability)scenarios:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onscenario
Permission (capability)scenarios:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Running a scenario requires scenarios:run alongside scenarios:read and scenarios:write. It executes the scenario's real actions.

Acts onscenario
Permission (capability)scenarios:run
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onscenario
Permission (capability)scenarios:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Executions & logs

List a scenario's run logs and read the details of a single execution.3

Acts onexecution log
Permission (capability)scenarios:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onexecution log
Permission (capability)scenarios:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Status is one of RUNNING, SUCCESS, WARNING, or ERROR.

Acts onexecution
Permission (capability)scenarios:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Connections

List, read, create, rename, and delete the connections to outside apps, and verify a connection.6

Takes a teamId query parameter to say which team's connections to list.

Acts onconnection
Permission (capability)connections:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onconnection
Permission (capability)connections:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Holds the credentials a scenario uses to reach the outside app.

Acts onconnection
Permission (capability)connections:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onconnection
Permission (capability)connections:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Removing a connection breaks any scenario that relied on it.

Acts onconnection
Permission (capability)connections:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Verifying a connection needs connections:write, not just read.

Acts onconnection
Permission (capability)connections:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Data stores

List, create, update, and delete data stores, and read, write, and delete the records inside them.8

Takes a teamId query parameter to say which team's data stores to list.

Acts ondata store
Permission (capability)datastores:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ondata store
Permission (capability)datastores:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ondata store
Permission (capability)datastores:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ondata store record
Permission (capability)datastores:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ondata store record
Permission (capability)datastores:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

PUT replaces the whole record; PATCH leaves unprovided fields unchanged.

Acts ondata store record
Permission (capability)datastores:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ondata store record
Permission (capability)datastores:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

A bulk delete of all records needs the confirmed=true query parameter.

Acts ondata store record
Permission (capability)datastores:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Hooks (triggers)

List, create, update, and delete inbound hooks, and enable, disable, or ping them.8

A hook is an inbound trigger that starts a scenario from an outside request or email.

Acts onhook
Permission (capability)hooks:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onhook
Permission (capability)hooks:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onhook
Permission (capability)hooks:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onhook
Permission (capability)hooks:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Deleting a hook stops the trigger that started its scenario.

Acts onhook
Permission (capability)hooks:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onhook
Permission (capability)hooks:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onhook
Permission (capability)hooks:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onhook
Permission (capability)hooks:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Teams

List the teams in an organization, read a team, and create a team.3

Takes an organizationId query parameter to say which organization to read.

Acts onteam
Permission (capability)teams:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onteam
Permission (capability)teams:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Requires the name and organizationId fields.

Acts onteam
Permission (capability)teams:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Organizations

List organizations, read an organization, and create an organization.3

Acts onorganization
Permission (capability)organizations:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

The license object's apiLimit reports the organization's per-minute request ceiling.

Acts onorganization
Permission (capability)organizations:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Creating an organization also needs the admin:write scope.

Acts onorganization
Permission (capability)organizations:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Users

List the users in an organization or team, and find users by permission.2

Takes a query parameter for the organization or team to read.

Acts onuser
Permission (capability)user:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts onuser
Permission (capability)user:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Templates

List templates, read a template, read its blueprint, and create a template.4

Acts ontemplate
Permission (capability)templates:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ontemplate
Permission (capability)templates:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ontemplate
Permission (capability)templates:read
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply

Acts ontemplate
Permission (capability)templates:write
VersionAvailable since the API’s base version
Webhook eventNone
Rate limitStandard limits apply
No endpoints match those filters.
Webhooks

Webhook events.

Make's hooks are inbound triggers, not outbound notifications. A hook receives an HTTP request or an email from an outside service and starts a scenario, and the API lists, creates, and manages those hooks rather than registering a receiver for Make's own events.

EventWhat it signalsTriggered by
No events match that search.
Rate limits & pagination

Rate limits, pagination & request size.

Make limits how fast an app or AI agent can call, through a per-minute request quota that depends on the organization's plan, from Core up to Enterprise.

Request rate

Make sets a request limit per minute, decided by the organization's plan. Core gets 60 requests per minute, Pro gets 120, Teams gets 240, and Enterprise gets 1,000. The limit is per organization, and exceeding it returns 429 with the message that the requests limit for the organization was exceeded. An organization's current ceiling is reported as the apiLimit property in the license object returned by getting that organization.

Pagination

Most endpoints that return a collection are paginated. The pg[limit] and pg[offset] query parameters set the page size and starting point, and pg[sortBy] and pg[sortDir] set the sort. The square brackets must be URL-encoded. Some list endpoints require a teamId or organizationId query parameter to say which team or organization to read.

Request size

Requests and responses are JSON. A request that exceeds the server's size limits returns 413 Payload Too Large, for example an oversized upload. The API does not publish a single global payload size ceiling across every endpoint.

Errors

Status codes & error handling.

The status codes an agent should handle, and what to do about each.

StatusCodeMeaningWhat to do
400Bad RequestThe request could not be understood, with invalid syntax or data, such as a bad data type, a prohibited duplicate, an invalid connection type, or a failed file validation.Read the detail and code in the response body, correct the request, and resend.
403ForbiddenThe request was authenticated but not permitted. The token lacks the access or the scope the endpoint requires.Grant the missing scope or use a token whose user has access to the team or organization.
404Not FoundThe resource cannot be found, such as a nonexistent or removed scenario, team, template, user, organization, or app. Make may also return 404 instead of 403 to hide a resource from a client that cannot see it, and a wrong-case path triggers it too.Confirm the path, its case, and that the token can see the resource.
413Payload Too LargeThe request entity exceeded the limits set on the server, for example an oversized upload.Reduce the size of the request body and resend.
424Failed DependencyThe request failed because a previous request it depended on failed, such as a connection action that crashed or timed out.Resolve the underlying failure, then retry the request.
429Too Many RequestsThe organization exceeded its per-minute request limit. The body message states that the requests limit for the organization was exceeded.Slow the request rate to within the plan's per-minute limit, then retry.
503Service UnavailableA dependency the request needs is currently unavailable.Wait and retry, since the condition is usually temporary.
Versioning & freshness

Version history.

Make does not version its API by date. There is a single, current major version of the API, kept up to date in place, and changes ship through the developer hub and changelog.

Version history

What changed, and when

Latest versionv2
v2Current version
Current API (version 2)

Version 2 is the current major version of the Make API, reached at https://{zone}.make.com/api/v2. Make does not version the API by date, so there is no version header to pin. The API is kept up to date in place, and notable changes ship through the developer hub. Make is the successor to Integromat, and the v2 API is the modern interface used today.

What changed
  • Resource-oriented endpoints for scenarios, connections, data stores, hooks, teams, organizations, users, and templates
  • Granular per-token scopes chosen at token creation
  • Regional zone hosts in the base URL, such as eu1, eu2, us1, and us2
  • A first-party hosted Model Context Protocol server that turns scenarios into agent tools

An integration calls the current major version directly, with no version header to pin.

Make API documentation ↗
Questions

Make API, answered.

How does authentication work, and where does the token come from?+
Calls use an API token sent in the Authorization header as 'Token '. The token is a user authentication token created in the Make profile, and its scopes are chosen at creation. A token reaches only the organizations and teams its user belongs to. OAuth 2.0 is also available for apps acting on a user's behalf, using the authorization code flow with refresh tokens for confidential clients and PKCE for public clients.
What are the API scopes, and how do they work?+
Make uses granular scopes in the form area:access, such as scenarios:read, scenarios:write, scenarios:run, connections:write, datastores:read, hooks:write, and organizations:read. The scopes are selected when the token is created, so the token can do only what those scopes allow. A call to an endpoint whose scope is missing is rejected. Running a scenario, for instance, needs scenarios:run in addition to read and write.
What is the base URL, and why does it have a region in it?+
The base URL is https://{zone}.make.com/api/v2, where {zone} is the zone the organization lives in, such as eu1, eu2, us1, or us2. Make hosts organizations in regional zones, so a call must go to the zone that holds the target organization rather than one global domain. The zone is visible in the URL of the Make web app.
What are the rate limits?+
Make limits requests per minute by the organization's plan: 60 for Core, 120 for Pro, 240 for Teams, and 1,000 for Enterprise. The limit counts against the whole organization, not a single token. Going over returns 429 with a message that the organization's request limit was exceeded. The current ceiling for an organization is returned as apiLimit in the license object when that organization is fetched.
Are Make's hooks the same as outbound webhooks?+
No. A Make hook is an inbound trigger. It receives an HTTP request or an email from an outside service and starts a scenario, rather than Make sending an event out to a receiver. The hooks endpoints list, create, update, and delete those triggers, and ping reports whether a hook is attached, learning, or inactive. Learn start and learn stop let a hook detect the structure of incoming data.
Does Make have an MCP server for AI agents?+
Yes. Make hosts its own server for the Model Context Protocol, the standard way an AI agent calls an outside system. It turns active and on-demand scenarios into tools an agent can run, and can also manage account elements like connections, hooks, and data stores. It connects over streamable HTTP or server-sent events at mcp.make.com using OAuth, or at a zone host using an MCP token. Running scenarios is available on all plans; management tools need a paid plan.
How does the API report errors?+
Errors use standard HTTP status codes and a JSON body with detail, message, and code fields, where code is a Make-specific identifier such as SC403 or IM005. A 400 means the request was malformed or invalid, 403 means the token lacks access, 404 means the resource does not exist or is hidden, 429 means the rate limit was exceeded, and 503 means a dependency is unavailable.
Related

More developer API guides for agents

What is Bollard AI?

Control what every AI agent can do in Make.

Bollard AI sits between a team's AI agents and Make. Grant each agent exactly the access it needs, read or write, scenario by scenario, and every call is checked and logged.

  • Set read, write, or full access per agent, never a shared Make token.
  • Denied by default, so an agent reaches only what has been explicitly allowed.
  • Every call recorded in plain English: who, what, where, and the decision.
Make
Ops Agent
Read scenarios ResourceOffReadFull use
Run a scenario ActionOffReadFull use
Manage connections ResourceOffReadFull use
Per-agent access, set in Bollard AI, not in Make