> For the complete documentation index, see [llms.txt](https://docs.mburger.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mburger.cloud/api-docs-1/introduction/getting-started.md).

# Getting Started

Before starting, make sure to have access to an existent project (with an admin or developer role) or create a new [MBurger project](https://mburger.cloud/register).

After that, navigate to Settings > **API Keys** to create an auth token, which you will need to interact with the APIs.

{% hint style="info" %}
Be aware that for most use cases you should obtain an API key with **read** permission. If you will use creation or editing API you'll need to add **write** and **delete** permissions.
{% endhint %}

The MBurger API is organized around REST, resource-oriented URLs and JSON responses. It aims to facilitate the life of the developer offering a robust query and filtering system through URLs.

Use HTTPS when calling all methods.

All media files are served by the CloudFront CDN through `https://cdn.mburger.cloud`.

{% hint style="info" %}
Is highly suggested to familiarize yourself with the structure of an MBurger project and to **read** the [Common](https://docs.mburger.cloud/api-docs/common) section before start exploring the APIs documentation.
{% 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://docs.mburger.cloud/api-docs-1/introduction/getting-started.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.