> 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/authenticate-the-make-cli.md).

# Authenticate the Make CLI

Before you can run commands, you must connect the Make CLI to your Make account. Your authentication options are the login wizard, environment variables, or per-command options.

### Login wizard (recommended)

The login wizard saves your credentials locally, so you don't have to pass them with every command.

To start the wizard, run:

```bash
make-cli login
```

The wizard guides you through the following steps:

1. Select your zone (for example, `EU1`).
2. If you don't have a Make API key, create one in the Make API key page that opens in your browser.
3. Enter your API key.

Your credentials are saved to the following location, depending on your operating system:

| Operating system | Credentials location             |
| ---------------- | -------------------------------- |
| macOS / Linux    | `~/.config/make-cli/config.json` |
| Windows          | `%APPDATA%\make-cli\config.json` |

Once authenticated, all commands work without extra options.

The Endpoints CLI included in `@makehq/endpoints-sdk` can reuse the credentials saved by `make-cli login`. It has no separate login command. For non-interactive use, provide both `MAKE_API_KEY` and `MAKE_ZONE`. See [Make Endpoints CLI](https://developers.make.com/make-cli/make-endpoints-cli.md) for authentication precedence and beta requirements.

#### Authentication status

To confirm which account you're signed in to, run:

```bash
make-cli whoami
```

#### Log out

To remove your saved credentials, run:

```bash
make-cli logout
```

### Environment variables

To set your API key and zone as environment variables:

```bash
export MAKE_API_KEY="your-api-key"
export MAKE_ZONE="MAKE_ZONE"
```

### Per-command options

To pass your credentials directly with each command using the `--api-key` and `--zone` options:

```bash
make-cli --api-key your-api-key --zone MAKE_ZONE scenarios list --team-id 1
```

### Authentication priority

If you use more than one authentication method, the Make CLI resolves credentials in the following order:

1. Per-command options
2. Environment variables
3. Saved credentials from the login wizard


---

# 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/authenticate-the-make-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.
