> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/settings/api-settings.md).
# API Settings
API keys are essential for integrating third-party applications such as Zapier. In this section, you can create and manage your API keys to ensure smooth integration.
To access the API settings:
1. Navigate to the Dashboard.
2. Click on the **Settings** icon in the left-side menu.
3. Then, select "**API Settings**"
API Settings
### Create an API Key
To create an API key, follow these steps:
1. Click the "**Add API Key**" button located on the right side.
2. Enter the name for the API token (for example: *Zapier*, *MyApp1*, etc) and click “**Generate**.”
3. Once the API Key and API secret are generated, you can **Download** them to your device for future use.
Create an API Key
{% hint style="info" %}
Securely store the API Secret as it is only available once for further use.
{% endhint %}
### Delete an API Key
To delete an API Key, first, click the trash button situated beside the API Key you wish to delete. Then, click the "**Delete**" button from the popup.
Delete an API Key
{% hint style="info" %}
Once an API key has been deleted, it cannot be restored.
{% 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://help.docupilot.app/settings/api-settings.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.
