> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/v1/get-started/create-api-key.md).

# Manage V1 API Keys

{% hint style="danger" %}
Mindee V1 API keys are **not compatible** with [Mindee V2](https://docs.mindee.com/) APIs.
{% endhint %}

## Overview

You will need to create a V1 API key to make API requests on Mindee V1.

All Products can be accessed using a single API key.

This includes [docTi](/v1/docti/docti-overview.md) and all [Off-the-Shelf](/v1/off-the-shelf-products/what-is-off-the-shelf-api.md) products such as Financial Document API, Invoices API, Receipts API, Bank Account Details API, \&c...

## Create Your V1 API Key

Once logged in, you'll land on **My APIs** page where you will have access to the APIs you are using and a button **Document Catalog** to explore the off-the-shelf APIs proposed by Mindee.

<figure><img src="/files/aeOPCcYC6ySujm3lGjt2" alt="" width="563"><figcaption></figcaption></figure>

1. Click on API keys on the left menu, or click on the button below:\ <a href="https://platform.mindee.com/api-keys" class="button primary">Go to API Keys</a>
2. Click on **Create a new API key** button.

<figure><img src="/files/T5FslvnPsVayxEhvsVVM" alt="" width="563"><figcaption></figcaption></figure>

3\. Give your API key a desired name and click on **Create API key**.

<figure><img src="/files/aFwSXVWpSQo5KainTAbX" alt="" width="563"><figcaption></figcaption></figure>

4. Your API key will be created showing the date and time it was created. You can then copy your API key and paste it into your development environments, applications, or command-line tools.

<figure><img src="/files/T6auFWOoOPXtXJML8ujw" alt="" width="563"><figcaption></figcaption></figure>

## Manage V1 API keys

Within the API keys section, you can create multiple API keys according to your needs, retrieve, and delete your API keys.

### Set up Another V1 API Key

You may want to use different keys for different environments, for example, one key for development, another for staging, another for production, etc. They can be different scenarios in this regard.

To add another API key, click on the **Create a new API key** button.

<figure><img src="/files/26yOGw1jXAsrOE2Oxw4U" alt="" width="563"><figcaption></figcaption></figure>

You can create multiple keys according to your needs and each of these keys can work across all APIs.

<figure><img src="/files/WIpzpT9fgD5tx1HiEgqS" alt="" width="563"><figcaption></figcaption></figure>

### Delete a V1 API key

{% hint style="warning" %}
It is important to note that if you delete your API keys, it cannot be undone.
{% endhint %}

Once your API key is created, the API key can be deleted, but not modified.

1. Click on the delete icon located on the left.

<figure><img src="/files/jsQYlPjKPYPyfj1XZ4SZ" alt="" width="563"><figcaption></figcaption></figure>

2. A dialog box will pop out, type the name of your API key and click on the **Delete API** button.

<figure><img src="/files/IY4WlpD2zU0OaRzNmUkm" alt="" width="563"><figcaption></figcaption></figure>

## Best Practices for Using API Keys

1. Keeping your API keys in your environment variables is a good and safe practice.
2. Don’t store your API key directly in your code.
3. Avoid exposing your secret API keys on GitHub, on the client-side, or in any other location that is open to the public.
4. Periodically change your API keys. To do so:
   * Create a new API key,
   * Update your application with the new API key.
   * Delete the old API key.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mindee.com/v1/get-started/create-api-key.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.