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

# Developer API

Create API keys for working with Zerve programmatically.

Create **API keys** for Zerve in **Settings → Developer API**. API keys let tools and scripts work with Zerve on your behalf.

## Creating an API key

1. Go to **Settings → Developer API**.
2. Create a new key, and copy it straight away.
3. Store it somewhere secure, such as a secrets manager.

{% hint style="warning" %}
An API key acts as you, with your permissions. Never share it or commit it to a code repository. If a key may have been exposed, delete it and create a new one.
{% endhint %}

## Where API keys are used

| Use                             | Details                                                                                                      |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Setting up AWS self-hosting** | The [AWS QuickStart](/zerve-docs/self-hosting/aws-quickstart.md) needs an API key from an organization admin |


---

# 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.zerve.ai/zerve-docs/administration/developer-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.