> 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/api-documentation/getting-started/api-structure.md).

# Make API structure

The URL of the Make API consists of three parts:

```
https://{zone_url}/api/{api_version}/{api_endpoint}
```

for example:

```
https://eu1.make.com/api/v2/users/me
```

### Base URL

Base URL is the core part of an API URL. API endpoint URLs are always relative to the base URL.

The `{zone_url}/api/{version}` form the base URL of the Make API. For example, the URL `https://eu1.make.com/api/v2` is a base URL for the Make API for organizations in the EU1 zone.

### **Zone URL**

The zone URL refers to the geological location of the region and environment of your Make organization. Typically, this URL is connected with the infrastructure region (for example, The United States or Europe) and the pricing plan your organization (the Enterprise pricing plans or others).

You can find out the base URL for your organization in the URL address bar of your Make organization dashboard:

<figure><img src="/files/aMvW0RLAqTJCZnmFwnuJ" alt=""><figcaption></figcaption></figure>

Example Make zone URLs:

* `https://eu1.make.com/`
* `https://eu2.make.com/`
* `https://eu1.make.celonis.com/`
* `https://us1.make.com/`
* `https://us2.make.com/`
* `https://us1.make.celonis.com/`

{% hint style="info" %}
Make sure to use the correct base URL when running API calls otherwise your API requests will fail.
{% endhint %}

### **API version**

The version of the API. The Make API is currently the second version.

### **API endpoint**

Each endpoint represents a resource you can work with. Endpoints may contain required or optional parameters. The resources are described in detail in [Make resources](/api-documentation/getting-started/resources.md).

{% hint style="info" %}
As a security best practice, make sure to use the correct case for your endpoints to work. You should review your scenarios to ensure that all API endpoints use the exact casing specified in the API documentation. Using incorrect casing, such as `/v2/Organizations` instead of `/v2/organizations`, or any other variation will cause the request to fail.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.make.com/api-documentation/getting-started/api-structure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.