> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/make-cli/make-endpoints-cli.md).

# Make Endpoints CLI

{% hint style="warning" %}
Endpoints are in **closed beta**. Make must [enable Endpoints for your organization](https://tally.so/r/0Q2149) before you can call them.
{% endhint %}

Use the Make Endpoints CLI to inspect available app actions and execute an Endpoint from your terminal or a script. This command is included in `@makehq/endpoints-sdk`, alongside the TypeScript SDK.

To manage scenarios, teams, connections, and other Make resources, use the standard [Broken mention](broken://spaces/1hrvjgtxJweadHEGZubd/pages/Lnb2R3KdoPXmKwbQA7Zy).&#x20;

### Install

Use Node.js 24 or 26, then install the package globally:

```bash
npm install -g @makehq/endpoints-sdk
make-endpoints-cli --help
```

To run it without a global installation, use npm's package option:

```bash
npx --package=@makehq/endpoints-sdk make-endpoints-cli --help
```

For repeatable scripts and agent environments, pin a tested version.&#x20;

### Authenticate

The Endpoints CLI doesn't have its own login command. [Install the Make CLI](https://developers.make.com/make-cli/make-cli/install-the-make-cli) if you haven't already, then run its login wizard once:

```bash
make-cli login
```

Alternatively, set `MAKE_API_KEY` and `MAKE_ZONE` as environment variables.&#x20;

The Endpoints CLI resolves credentials in this order:&#x20;

1. Command flags
2. Environment variables
3. Saved login ( `make-cli login` )

The CLI uses the saved login only if you haven’t set an API key or a zone with a flag or an environment variable. For example, if you set only `MAKE_ZONE`, the CLI doesn’t take the key from the saved login.

For unattended scripts or agents, load the environment variables from a secrets manager. Avoid putting API keys in command arguments, prompts, or logs. Use a hostname such as `us1.make.com` for the zone.

Your API key needs `endpoints:run`, and the caller must have access to the selected team and connection.&#x20;

### Discover apps and Endpoints

View the local catalog with `list`:

```bash
make-endpoints-cli list
make-endpoints-cli list google-docs
make-endpoints-cli list google-docs v1
```

View an Endpoint before calling it with `describe`:

```bash
make-endpoints-cli describe google-docs v1 get-document
```

The command returns the Endpoint definition, including its input schema, accepted connection types, required provider scopes, and usage notes for agents.&#x20;

To include the output schema, add `--output-schema`:

```bash
make-endpoints-cli describe google-docs v1 get-document --output-schema
```

{% hint style="info" %}
Output schemas can be large, so request them only when needed.&#x20;
{% endhint %}

`list` and `describe` show what comes with the installed CLI. Endpoints appear in `list` even if your team doesn't have access to them. To find a connection that works with an Endpoint:

1. List your team’s connections with the Make CLI, and replace `123` with your team ID:

```bash
make-cli connections list --team-id 123 --output json
```

2. Check compatibility against the Endpoint definition (run `describe`) before running an Endpoint.&#x20;

### Run an Endpoint

To run an endpoint, use this command structure:

```
make-endpoints-cli <app> [v<N>] <endpoint> [options]
```

Omitting the version selects the app's latest version in the installed package. Specify it when a script depends on a particular input contract.

For example, retrieve a Google Docs document:

```bash
make-endpoints-cli google-docs v1 get-document \
  --team-id 123 \
  --connection-id 456 \
  --input '{"documentId":"YOUR_DOCUMENT_ID","filter":"image"}' \
  --output json
```

Replace the example team ID, connection ID, and document ID with your values. This Endpoint's generated input type requires `field`.

Use `--input` for the complete business-input object. Supported input fields can also be supplied as individual flags. Those flags override the same keys in `--input`. Pass fields that conflict with CLI option names inside `--input`.

### Call an Endpoint by name

Use `endpoints execute` to run Endpoints that don't have their own command, such as those for custom apps. It doesn't discover or infer their input schemas.

```bash
make-endpoints-cli endpoints execute \
  --app-name 'app#my-app' \
  --app-version 1 \
  --endpoint-name listContacts \
  --team-id 123 \
  --connection-id 456 \
  --input '{"limit":10}' \
  --output json
```

This example shows the command’s format. Replace the app name, Endpoint name, IDs, and input with values for your own Endpoint.

### Output and errors

Use `--output json` for machine-readable output. `compact` and `table` are also supported.

API-call failures exit with code `2`, and all other errors exit with code `1`.

If an Endpoint won’t run, check the following:

* The Endpoints beta is enabled for your organization.
* `MAKE_ZONE` matches the zone your team is in.
* Your API key has the `endpoints:run` scope.
* Your account has access to the team and connection.

Before retrying an Endpoint that creates, updates, or deletes data, check whether the change already happened to avoid duplicates.&#x20;

For agent-specific guidance on outputs, see [Use Make CLIs with AI agents](https://developers.make.com/make-cli/use-make-clis-with-ai-agents.md).

### Resources

* [npm: @makehq/endpoints-sdk](https://www.npmjs.com/package/@makehq/endpoints-sdk)
* [GitHub: make-endpoints-sdk](https://github.com/integromat/make-endpoints-sdk)
* [Make Endpoints SDK](https://developers.make.com/make-sdk/make-endpoints-sdk.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.make.com/make-cli/make-endpoints-cli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
