> For the complete documentation index, see [llms.txt](https://docs.velafi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velafi.com/velafi-1/guides/creating-api-key/safely-store-your-api-key.md).

# Safely Store Your API Key

<figure><img src="https://1555040221-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV9hKdCChTHquQ6LtTGc9%2Fuploads%2FhREulqwSMIa7YpVh3rBS%2Fimage.png?alt=media&amp;token=7eba5ca6-7115-4308-a266-19fe2b2f1cc2" alt=""><figcaption></figcaption></figure>

Interface shows that the **API Key created**.&#x20;

## **⚠️Notes**

#### **Uniqueness:**

Each API key is unique and specifically designed for accessing VelaFi’s production environment.

#### **Storage Recommendations:**

<mark style="color:orange;background-color:orange;">Immediately store your API key in a secure location after generating it, as you will not be able to view it again once you leave the page.</mark>

<mark style="color:orange;background-color:orange;">Do not store your API key on public devices or in public locations, and avoid saving it in plaintext format.</mark>

<mark style="color:orange;background-color:orange;">Recommendation: Use encryption tools or a password manager to securely store your API key and prevent accidental exposure.</mark>


---

# 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.velafi.com/velafi-1/guides/creating-api-key/safely-store-your-api-key.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.