> 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/product-guides-and-integrations/product-guides/export-apis.md).
# Export APIs
Export Luciq app health metrics by API, including crash-free sessions, launches, OOMs, and ANRs, into Grafana, Datadog, or your dashboards.
### Exporting App Health Metrics via API
To help teams unify their observability and performance workflows, Luciq offers API access to export app health metrics—including crash-free sessions, cold and hot app launches, OOMs, ANRs, and more. This enables you to integrate Luciq insights into your preferred monitoring tools such as **Grafana**, **Datadog**, or internal dashboards.
#### Who Can Access These APIs?
Access to the App Health Metrics Export API is **exclusive to Enterprise plans**.
#### How to Get Started
If you are on an Enterprise plan and would like to enable this integration:
* Please contact your **Customer Success Manager** or reach out to our **Support team** at .
* A team member will assist you with authentication and provide access to the detailed API reference, including available endpoints, supported metrics, and sample payloads.
{% hint style="info" %}
**Authentication is required to access the export API. Your CSM or Support contact will guide you through obtaining the necessary credentials.**
{% 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/export-apis.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 `build a script that syncs our docs to a CMS` 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.
