> 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/user-documentation/connect/api-documentation.md).
# API Documentation
Access the Daxium-Air REST API for custom integrations and advanced automation.
Daxium-Air provides a comprehensive **REST API** for developers who need to build custom integrations or automate workflows programmatically.
## What you can do
* **Read** submissions, structures and user data
* **Create and update** submissions programmatically
* **Search** submissions with advanced filters
* **Manage** users and groups
* **Generate** reports on demand
## Authentication
The API uses **OAuth token-based authentication**. You will need an API key and secret generated from your Daxium-Air back-office, together with a user's username and password, to generate an OAuth token. That token is then used to authenticate your requests.
1. Under Webservices > API Keys , click on the "+ New" button to create a new API Key & Secret
2. Then enter a description to name your key and click on save (you don't need to edit the remaining fields"
## Permissions
To use the API, the authenticated user must have the **Mobile** [licence](/user-documentation/components-concepts-terminology.md#licence) enabled. Rights on forms, submissions, [groups](/user-documentation/components-concepts-terminology.md#group), and so on are inherited from that user, exactly as they would be in the app.
{% hint style="info" %}
The **Web Reader** and **Web Contributor** licences have no effect on API access. For example, a user with both the Mobile and Web Reader licences can still create and edit submissions through the API.
{% endhint %}
## Getting started
1. Generate an [**authentication token**](https://www.center.daxium-air.com/api-reference/authorization) using the API key and secret, together with the username and password of the user you want to authenticate as
2. Include the authentication token in the `Authorization` header of your requests
3. Refer to the API reference for available endpoints
{% hint style="info" %}
The full API reference is available in the [**API Reference**](https://www.center.daxium-air.com/api-reference) section of this documentation site.
{% 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 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/user-documentation/connect/api-documentation.md?ask=&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.
