> For the complete documentation index, see [llms.txt](https://docs.opendatablend.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opendatablend.io/subscription-management/managing-access-keys.md).
# Managing Access Keys
Access Keys are used to make authenticated requests to the [Open Data Blend Dataset API](/open-data-blend-datasets/dataset-api.md). Whenever you use one of your access keys to request a data file, the usage will be associated with your Analytics Plan subscription. Without an access key, the number of data file requests that you can make is [limited](/open-data-blend-datasets/dataset-api.md#usage-limits).
{% hint style="info" %}
When starting a new Analytics Plan subscription, you may have noticed two fields called 'Access Key 1' and 'Access Key 2' on the Analytics Plan checkout page. These are presented but should be left blank. Your access keys will only be generated after you have successfully started your subscription.
In the future, these blank access key fields will no longer be presented during the Analytics Plan sign-up process.
{% endhint %}
{% hint style="danger" %}
Access Keys are a type of secret. Keep them safe and ensure that they are not shared with any unauthorised persons. If you believe that either of your access keys have been compromised, you should raise a request to have them [rotated](/subscription-management/managing-access-keys.md#rotating-access-keys) immediately.
{% endhint %}
## Viewing Access Keys
You can view your access keys in the subscription portal by clicking the ’View More’ link on the Home page.
Both access keys will be visible in plain text so ensure that your screen is not visible to any unauthorised persons.
Once you have copied and saved the access keys to another secure location (e.g. a password manager or key vault), we **strongly recommend** that you remove them from the portal. This can be done by clicking the edit button in the Account Details section, blanking out the access key values, and then clicking ’Save’.
{% hint style="info" %}
Strong encryption is used to store access keys in the subscription portal database. The actual values are only visible in the portal and are decrypted on-the-fly. We only store access key prefixes and hashes in the access key authentication system.
{% endhint %}
## Using Your Access Keys
For guidance on how to use your access keys, please see the [Data File](/open-data-blend-datasets/dataset-api.md#data-file) section of the Open Data Blend Dataset API.
## Rotating Access Keys
If you would like to rotate your access keys from time to time to keep in-line with security best practices, please use the 'Send Email' button in the subscription portal to raise a support request. When raising the request, include your subscription number, the name of the access key number that you wish to be regenerated (i.e. 'Access Key 1' or ’Access Key 2'), and ensure that you have updated your applications to use the alternate access key, where applicable.
{% hint style="success" %}
We will always confirm the access key number to be regenerated before completing the request.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.opendatablend.io/subscription-management/managing-access-keys.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 `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.
