Make

Make Scenarios API

The Scenarios API from Make — 6 operation(s) for scenarios.

Documentation GitHub OpenAPI

Operations 10

GET /scenarios List all scenarios #

POST /scenarios Create a new scenario #

GET /scenarios/{scenarioId} Get scenario details #

PATCH /scenarios/{scenarioId} Update scenario #

DELETE /scenarios/{scenarioId} Delete scenario #

GET /scenarios/{scenarioId}/triggers Get trigger details #

POST /scenarios/{scenarioId}/clone Clone scenario #

GET /scenarios/{scenarioId}/interface Get scenario inputs/outputs specification #

PATCH /scenarios/{scenarioId}/interface Update scenario inputs specification #

GET /scenarios/{scenarioId}/usage Get scenario usage statistics #

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/make/refs/heads/main/openapi/make-scenarios-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/make-scenarios-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Make AI Agents Scenarios API
  description: The Make (formerly Integromat) REST API provides programmatic access to scenarios and the broader Make platform. Endpoints are organized into resource-oriented URLs at `/api/v2/`. Authentication uses an API token issued from the user profile with required scopes, passed via the `Authorization` header (`Token <api-token>`).
  version: 2.0.0
  contact:
    name: Make
    url: https://developers.make.com/api-documentation
servers:
- url: https://us1.make.com/api/v2
  description: US1 region
- url: https://us2.make.com/api/v2
  description: US2 region
- url: https://eu1.make.com/api/v2
  description: EU1 region
- url: https://eu2.make.com/api/v2
  description: EU2 region
security:
- TokenAuth: []
tags:
- name: Scenarios
paths:
  /scenarios:
    get:
      tags:
      - Scenarios
      summary: List all scenarios
      operationId: listScenarios
      responses:
        '200':
          description: Scenarios
    post:
      tags:
      - Scenarios
      summary: Create a new scenario
      operationId: createScenario
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '201':
          description: Scenario
  /scenarios/{scenarioId}:
    get:
      tags:
      - Scenarios
      summary: Get scenario details
      operationId: getScenario
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Scenario
    patch:
      tags:
      - Scenarios
      summary: Update scenario
      operationId: updateScenario
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Updated
    delete:
      tags:
      - Scenarios
      summary: Delete scenario
      operationId: deleteScenario
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      responses:
        '204':
          description: Deleted
  /scenarios/{scenarioId}/triggers:
    get:
      tags:
      - Scenarios
      summary: Get trigger details
      operationId: getScenarioTriggers
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Trigger details
  /scenarios/{scenarioId}/clone:
    post:
      tags:
      - Scenarios
      summary: Clone scenario
      operationId: cloneScenario
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      responses:
        '201':
          description: Cloned scenario
  /scenarios/{scenarioId}/interface:
    get:
      tags:
      - Scenarios
      summary: Get scenario inputs/outputs specification
      operationId: getScenarioInterface
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Interface
    patch:
      tags:
      - Scenarios
      summary: Update scenario inputs specification
      operationId: updateScenarioInterface
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Updated
  /scenarios/{scenarioId}/usage:
    get:
      tags:
      - Scenarios
      summary: Get scenario usage statistics
      operationId: getScenarioUsage
      parameters:
      - name: scenarioId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Usage stats
components:
  securitySchemes:
    TokenAuth:
      type: apiKey
      in: header
      name: Authorization
      description: 'API token in the form: `Token <api-token>` with the required scopes enabled.'