> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/api-reference/daxium-air-rest-api.md).

# Daxium Air REST API

Official API documentation for **Daxium Air**, version **v1.3**.

All calls must be encrypted using **TLS 1.2** or later, and every request must include the version header:

```
X-Accept-Version: v1.3
```

#### Authentication

The API uses **OAuth 2.0**. Every request (except token requests) must include a Bearer token:

```
Authorization: Bearer <access_token>
```

| Token           | Validity |
| --------------- | -------- |
| `access_token`  | 1 hour   |
| `refresh_token` | 42 days  |

#### Empty fields

As a general rule, a field with no value is **left out of the response entirely** — it is never sent as `"field": null`. A field described here as conditional or nullable simply means: absent from the JSON unless that condition is met.

#### Error format

All errors return a standardised JSON body:

```json
{
  "code": "DAERR-API1000",
  "message": "Invalid payload format",
  "url": "https://doc-dev.daxium-air.com/errors.en.html#DAERR-API1000",
  "api_version": "v1.3",
  "infos": [],
  "server_time": "1760616000"
}
```


---

# 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://www.center.daxium-air.com/api-reference/daxium-air-rest-api.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.