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

# Admin API

{% hint style="info" %}
This feature is only available on the Enterprise plan.
{% endhint %}

The Admin API is a CRUD API for performing operations without going through the Dashboard UI.

You can manage experiments, feature flags, and more via the API.

If you have a feature request, please contact Hackle.

#### Authentication

All Admin API requests must include an authentication key in the HTTP header.

* Header Name: **X-HACKLE-ADMIN-API-KEY**

```
X-HACKLE-ADMIN-API-KEY: YOUR_API_KEY_HERE
```

The Admin API KEY requires a separate issuance. Please contact Hackle.


---

# 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.hackle.io/en/hackle-admin-api/admin-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.
