For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connections

In Make, you need to create a connection for most apps. Make then uses this connection to communicate with the third-party service and to authenticate your requests to the third-party service. The following endpoints allow you to create and manage connections.

List connections

get
/connections

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

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Query parameters
teamIdintegerRequired

The unique ID of the team whose connections will be retrieved.

Example: 22
type[]string[]Optional

Specifies the type of the connections to return details for. The connection type is defined in the accountName property and you can get it from the Get connection details endpoint.

Example: {"value":"airtable2"}
<connectionType>[]string[]Optional

Allows utilizing the scopes check. The particular connection type (<connectionType>) should be one of the types specified in the type[] parameter. The values are the scopes to check for the given connection type. You can send multiple <connectionType> values with corresponding arrays to check multiple connection types scopes at once. The result of the check is reflected in the scoped property of the returned connection object.

Example: {"value":["requestedScope","anotherRequestedScope"]}
Responses
200

Successful response

application/json
get/connections
200

Successful response

Create connection

post
/connections

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

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Query parameters
teamIdintegerRequired

The unique ID of the team whose connections will be retrieved.

Example: 1
Body
accountNamestringOptional

The connection name. The name must be at most 128 characters long and does not need to be unique.

accountTypestringOptional

The connection type corresponding to the connected app. For some connection types, this property may require providing additional properties in the request body, such as clientId and clientSecret, in order to authorize the connection and make it functional.

scopesstring[]Optional

The connection scope determining the module use. The format and number of available scopes vary depending on the accountType parameter.

accountVisibilitystring · enumOptional

Entity-tier visibility of the created connection. With locked the connection is restricted to its access list from the moment it is created, with the creator as its sole admin. Requires the Locked connections feature to be enabled for the organization; otherwise the request fails with IM903 (HTTP 400). When the access list cannot be provisioned, the request fails with HTTP 422 and the connection is not created. Omitted or team, the connection is visible to the whole team.

Default: teamPossible values:
Other propertiesanyOptional
Responses
200

Successful response

application/json
post/connections

List updatable connection parameters

get
/connections/{connectionId}/editable-data-schema

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.

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Responses
200

Successful response

application/json
editableParametersstring[]Optional
get/connections/{connectionId}/editable-data-schema
200

Successful response

Update a connection

post
/connections/{connectionId}/set-data

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.

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Body

The request body has to contain the parameters listed in the response from the API call GET /connections/{connectionId}/editable-data-schema and the new values associated with them.

Other propertiesanyOptional
Responses
200

Successful response

application/json
changedbooleanOptional
post/connections/{connectionId}/set-data
200

Successful response

Get connection details

get
/connections/{connectionId}

Retrieves details of a connection with a given ID.

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Query parameters
Responses
200

Successful response

application/json
get/connections/{connectionId}
200

Successful response

Delete connection

delete
/connections/{connectionId}

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

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Query parameters
confirmedbooleanOptional

Confirms the deletion if the connection is included in at least one scenario. Confirmation is required because the scenario will stop working without the connection. If the parameter is missing or it is set to false an error code is returned and the resource is not deleted.

Example: true
Responses
200

Successful response

application/json
connectionintegerOptional
delete/connections/{connectionId}
200

Successful response

Rename a connection

patch
/connections/{connectionId}

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

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Query parameters
Body
namestringOptional

The updated connection name. The name must be at most 128 characters long and does not need to be unique.

Responses
200

Successful response

application/json
patch/connections/{connectionId}
200

Successful response

Verify connection

post
/connections/{connectionId}/test

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

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Responses
200

Successful response

application/json
verifiedbooleanOptional
post/connections/{connectionId}/test
200

Successful response

Verify if connection is scoped

post
/connections/{connectionId}/scoped

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

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Body
scopestring[]Optional

The array with IDs of the scopes for a given connection. The scope ID of a specific connection can be retrieved from the Get connection details endpoint.

Responses
200

Successful response

application/json
post/connections/{connectionId}/scoped
200

Successful response

Lock connection

post
/connections/{connectionId}/make-locked

Restricts the connection's visibility to its access list (visibility: locked). The caller becomes the sole admin of the locked connection.

Caller rule: when the connection has an author, only the author can lock it. A legacy connection without an author can be locked by any team member with the account edit permission.

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.

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Responses
200

Successful response

application/json
post/connections/{connectionId}/make-locked

Make connection available to team

post
/connections/{connectionId}/make-team

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.

Required scopes
This endpoint requires the following scopes:
Authorizations
AuthorizationstringRequired

Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.

If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.

Path parameters
connectionIdintegerRequired

The ID of the connection. You can get connection ID's of all your connections with the the List connections endpoint.

Example: 128
Responses
200

Successful response

application/json
post/connections/{connectionId}/make-team

Last updated