# Authentication

Using the API needs and authentication with an API token.

## Methods

 There are two ways to transmit an token:

#### Request header

> Request header **`Api-Token`** is required

#### GET parameter

> GET parameter **`apiToken`** is required

## Token administration

Tokens are stored in the database table `rest_users`.

| Column     | Value                             |
| ---------- | --------------------------------- |
| name       | User name / Token info *optional* |
| api-token  | Token **required**                |
| api-rights | rw/r **required**                 |

{% hint style="info" %}
While installation user with token `t6PEqwkBpbdsf93osDSF913Bmcsd78pYWLtEgvs` is created.
{% endhint %}

## Permissions

It´s possible to set **read/write** (default) and only **read** permissions.

| Status | Permission             |
| ------ | ---------------------- |
| rw     | GET, PUT, POST, DELETE |
| r      | GET                    |

{% hint style="danger" %}
Before production remove test user from `rest_users` table.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.oxid-projects.com/oxid-rest-api/routes-1/authentication.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.