> 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/authentication.md).

# API Authentication

The MBurger APIs offers 2 authentication providers:

* **project**: identifies a single project. This authentication is always requested while using API. It's based on a token header to add in every request.

To authenticate with the *project* provider the request **must include** the following headers:

| Header            | Description                                      |
| ----------------- | ------------------------------------------------ |
| X-MBurger-Token   | Your generated API key from the dashboard        |
| X-MBurger-Version | MBurger API version, actual version is now **3** |
| Accept            | application/json                                 |

* **mobile**: identifies a single user in a project. It's available only when the *users* feature is enabled and is

  based on JWT token header to add in every request.

To authenticate with the *mobile* provider the request **must include** the following headers:

| Header        | Description      |
| ------------- | ---------------- |
| Authorization | Bearer *JWT*     |
| Accept        | application/json |

The JWT token is obtained through the authentication API.

{% hint style="info" %}
If you are using Android or iOS, you will find open source SDKs in order to make mobile development easier. You can find more information for [iOS](https://github.com/Mumble-SRL/MBurger-iOS) and [Android](https://github.com/Mumble-SRL/MBurger-Android).
{% 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/authentication.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.