> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/references/api-access.md).

# API Access

Query your Luciq data with the Query API. Pull crash, session, network, and bug data into your own scripts, internal dashboards, and CI checks.

#### Your data, in your own tools. <a href="#your-luciq-data-in-your-own-tools" id="your-luciq-data-in-your-own-tools"></a>

**API Access** lets you pull the same data you see in the Luciq dashboard into your own scripts, internal dashboards, data pipelines, and CI checks.

Use it to:

* Track crash free sessions per release in your own BI tool
* Fail a CI build when launch time on the latest version regresses
* Export network failure rates per endpoint into a weekly report
* Build internal tools on top of Luciq data without scraping the dashboard

#### Before You Start <a href="#before-you-start" id="before-you-start"></a>

You need three things to run your first query:

1. **An API key** for your company. Owners and admins create keys in the dashboard. See [Authentication](/references/api-access/authentication.md).
2. **Your application slug** (`application`), as it appears in the dashboard URL (`https://dashboard.luciq.ai/applications/<slug>/<environment>/…`). Example: `react-native-demo-app`. An app token in its place returns `403 app_not_allowed` on every call.
3. **The environment** you want to query, for example `production`

#### Dedicated environments <a href="#dedicated-environments" id="dedicated-environments"></a>

{% hint style="info" %}
If your company uses a dedicated Luciq environment, ask your account manager for your API host. Use it instead of `api.luciq.ai`.
{% 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://docs.luciq.ai/references/api-access.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.