Workflow automation · API

Make API

Make

Manage automation resources with a plan-dependent REST API.

Official documentation Download development spec

Most Make API endpoints require a paid subscription; confirm the target plan and scopes rather than assuming free-tier access.

MAKE / DEVELOPER FIELD GUIDE

Choose an interface. Define a verifiable result.

Company or project context, ten technical entry points and a practical analysis of every reference.

2026-10-08 · Integration not tested

Company / project overview

Original summary of official company or project statements; use the source for the full original page.

Make · About
Company	Make is an integration and automation development platform and is part of Celonis.
Mission	The company emphasizes visual creation, process automation and connecting business systems.
Developer role	The REST API manages Make resources; scenario modules connect the external services used by a business workflow.

Complete official About page ↗

About reference — TA analysis
Audience	Buyers, partners and product owners shortlisting an AI provider.
Our assessment	Use positioning and company history for initial fit. Obtain project-specific deployment, support and commercial terms separately.

Official sources reviewed; no live API, inference or benchmark was run. Expected results are proposed internal contracts.

Top 10 technical entry points

Ten documented technical entry points selected by developer task; not ten separate SDKs or an official ranking.

Choose by the work you need to complete
Interface	Purpose and audience
01 · AuthenticationAPI / SDK / developer guide	Authenticate using API tokens or OAuth connections.API developers
02 · Roles and scopesAPI / SDK / developer guide	Match API scopes to user roles and resources.Access-control designers
03 · Rate limitingAPI / SDK / developer guide	Plan API consumption within service limits.Synchronization engineers
04 · Pagination and sortingAPI / SDK / developer guide	Retrieve resource lists in ordered pages.Inventory sync teams
05 · ScenariosAPI / SDK / developer guide	Manage and run supported scenarios.Automation platform developers
06 · Scenario logsAPI / SDK / developer guide	Inspect execution logs for a scenario.Operations teams
07 · Scenario blueprintsAPI / SDK / developer guide	Inspect scenario definitions and versions.Release and migration teams
08 · ConnectionsAPI / SDK / developer guide	Manage supported third-party connection resources.Connector maintainers
09 · HooksAPI / SDK / developer guide	Manage webhook and mailhook resources.Event integration teams
10 · Incomplete executionsAPI / SDK / developer guide	Inspect and manage incomplete execution records.Recovery operators

Reference analysis

Capabilities summarize official documentation. Constraints and proposed tests are our engineering assessment.

API / SDK / developer guide

Authentication

Authentication · TA
Target audience	API developers
Documented capability	Authenticate using API tokens or OAuth connections.
Input → output	Authenticated HTTP request → resource response.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Token validity and resource authorization are separate checks.
Our suggested validation	Test expired credentials without recording secrets.

Official reference · Authentication ↗

API / SDK / developer guide

Roles and scopes

Roles and scopes · TA
Target audience	Access-control designers
Documented capability	Match API scopes to user roles and resources.
Input → output	Role and scope selection → allowed operations.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Assigning an admin scope does not grant a regular user admin status.
Our suggested validation	Verify permitted reads and rejected unauthorized writes.

Official reference · Roles and scopes ↗

API / SDK / developer guide

Rate limiting

Rate limiting · TA
Target audience	Synchronization engineers
Documented capability	Plan API consumption within service limits.
Input → output	Request load → accepted or limited responses.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Limits depend on the applicable plan and service rules.
Our suggested validation	Implement bounded backoff and monitor rate-limit responses.

Official reference · Rate limiting ↗

API / SDK / developer guide

Pagination and sorting

Pagination and sorting · TA
Target audience	Inventory sync teams
Documented capability	Retrieve resource lists in ordered pages.
Input → output	List options → page of records.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Changing records during pagination can affect consistency.
Our suggested validation	Check total coverage and duplicate handling across pages.

Official reference · Pagination and sorting ↗

API / SDK / developer guide

Scenarios

Scenarios · TA
Target audience	Automation platform developers
Documented capability	Manage and run supported scenarios.
Input → output	Scenario operation → configuration or execution response.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Activating a scenario can enable external actions; creation alone is not execution success.
Our suggested validation	Verify target team, run state and declared outputs.

Official reference · Scenarios ↗

API / SDK / developer guide

Scenario logs

Scenario logs · TA
Target audience	Operations teams
Documented capability	Inspect execution logs for a scenario.
Input → output	Scenario/log query → execution records.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Log availability and contents do not prove downstream business correctness.
Our suggested validation	Correlate execution IDs and inspect failed modules.

Official reference · Scenario logs ↗

API / SDK / developer guide

Scenario blueprints

Scenario blueprints · TA
Target audience	Release and migration teams
Documented capability	Inspect scenario definitions and versions.
Input → output	Scenario reference → blueprint.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	A blueprint is not a portable copy of all credentials and resources.
Our suggested validation	Check referenced connections and environment mappings before reuse.

Official reference · Scenario blueprints ↗

API / SDK / developer guide

Connections

Connections · TA
Target audience	Connector maintainers
Documented capability	Manage supported third-party connection resources.
Input → output	Connection request → connection metadata or verification.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Resource existence does not guarantee valid provider authorization.
Our suggested validation	Test revoked provider credentials and avoid secret disclosure.

Official reference · Connections ↗

API / SDK / developer guide

Hooks

Hooks · TA
Target audience	Event integration teams
Documented capability	Manage webhook and mailhook resources.
Input → output	Hook operation → hook configuration/state.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Hook receipt is distinct from scenario completion.
Our suggested validation	Check active state and correlate incoming event to execution.

Official reference · Hooks ↗

API / SDK / developer guide

Incomplete executions

Incomplete executions · TA
Target audience	Recovery operators
Documented capability	Inspect and manage incomplete execution records.
Input → output	Incomplete execution query → recoverable context.
Execution environment	Make API for the selected account zone, plan and token permissions
Our decision constraint	Retrying partial work can duplicate already-completed external operations.
Our suggested validation	Review prior side effects before any recovery or replay.

Official reference · Incomplete executions ↗

Make API overview

Make API overview · Supporting reference analysis
TA	Product and platform leads
Our validation advice	Check plan eligibility, account zone and required scopes before implementation.

Official reference · Make API overview ↗

04 / INPUT · EXPECTED OUTPUT · ACCEPTANCE

Expected results before implementation

Illustrative scenario-operation receipt; not native Make API JSON. No scenario was activated, executed or modified, and no third-party action was performed.

Illustrative contract · no API call or model execution · not measured provider output

Completed scenario

Expected behavior — illustrative, not executed
Input	Authorized scenario receives valid declared input.
Expected result	ok with terminal execution state and expected bundles.
Acceptance	Match execution logs and outputs before reporting business completion.

No matching records

Expected behavior — illustrative, not executed
Input	Valid resource list query finds nothing.
Expected result	ok with empty resources, not an authorization error.
Acceptance	Check pagination termination and preserve selected team context.

Accepted execution

Expected behavior — illustrative, not executed
Input	Run request accepted but downstream work remains.
Expected result	pending with execution reference.
Acceptance	Do not interpret request acceptance as delivery or persistence.

Scope denied

Expected behavior — illustrative, not executed
Input	Token lacks required scope or user role.
Expected result	error; no resource change.
Acceptance	Report required access without exposing token or auto-escalating.

Partial execution

Expected behavior — illustrative, not executed
Input	Later module fails after an earlier external action.
Expected result	partial/error with incomplete-execution context.
Acceptance	Reconcile prior operations before replay to prevent duplicate effects.

Map the expected result to your application

Map the actual SDK or service response into this proposed internal contract after integration. All IDs and values below are invented examples; no credentials or live requests are included.

Expected output JSON — illustrative, not measured · MakeAPI-expected-results.json

{
  "schema_version": "1.0.0",
  "example": true,
  "provider": "Make",
  "status": "ok",
  "input_id": "sample-001",
  "data": {
    "scenario_id": "example-scenario",
    "execution_id": "example-execution",
    "execution_state": "completed",
    "output_bundles": [
      {
        "part_id": "example-part",
        "route": "review"
      }
    ]
  },
  "error": null,
  "verification": "illustrative-only;not-provider-response"
}

Download specification, example and acceptance plan

Engineering handoff — our proposed contract and gates
Result interpretation	Successful transport or execution does not establish model accuracy. Preserve valid empty results separately from operational failure.
Reproducibility	Record model, runtime, configuration and input identifiers; agree quality and latency criteria before representative tests. No measured performance is claimed.
Operation boundary	Illustrative scenario-operation receipt; not native Make API JSON. No scenario was activated, executed or modified, and no third-party action was performed.

Development assessment

Supplier follow-up queue

Development concept · integration not tested

Provider capabilities above are based on official documentation or repositories. The proposed product, inputs, deliverable and acceptance criteria below are our development assessment.

Small prototype

Test one documented operation with a small real sample after access is confirmed. This is a development judgment, not a delivery estimate.

Proposed inputs: A sample event, authorized systems and one defined workflow transition.
Proposed deliverable: A visible job state and audit trail for a single workflow.
Acceptance criterion: A retried event must not create duplicate work; an unavailable upstream must remain visibly pending or failed.
Dependencies: Runtime access, workflow permissions and a reviewed notification or write destination.

Integration condition

Most Make API endpoints require a paid subscription; confirm the target plan and scopes rather than assuming free-tier access.

Development sequence

Confirm access to Make API, license and the exact supported version.
Prepare the sample above and implement one documented operation for “Supplier follow-up queue”.
Normalize the result with source, time and explicit error state; keep the provider response for review.
Run the acceptance criterion before estimating rollout effort or committing a customer deliverable.

How to validate demand

Record product views, documentation clicks, specification downloads and contextual hub clicks. These are event counts, not unique people or completed integrations.

This feasibility assessment uses implementation conditions. No traffic-based rank or delivery-time promise is assigned.

Make API

Choose an interface. Define a verifiable result.

Company / project overview

Top 10 technical entry points

Reference analysis

Make API overview

Expected results before implementation

Completed scenario

No matching records

Accepted execution

Scope denied

Partial execution

Map the expected result to your application

Supplier follow-up queue

Integration condition

Development sequence

How to validate demand

Related products