> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/developer-tools/cerby-api/view-the-details-of-an-api-key.md).

# View the details of an API key

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, and **Admins**
* API key **Owners**
* Only supported using the Cerby web app
  {% endhint %}

To view the details of an active API key, you must complete the following steps:

1. Log in to your corresponding [Cerby](https://app.cerby.com/) workspace.
2. Select the **Settings** option from the left navigation drawer. The **Workspace Configuration** page is displayed.
3. Activate the **API keys** tab. A table of API keys is displayed.
4. Click the **More options** (...) icon of the corresponding key. A drop-down list is displayed.
5. Select the **API key settings** option from the list. The API key details page is displayed.

{% hint style="danger" %}
**IMPORTANT:** Cerby does not display the API key because it was hashed and stored; you can only view its name, the dates when it was created and last used, and its expiration date. You can also [update its scopes](/developer-tools/cerby-api/update-the-scopes-of-an-api-key.md).
{% endhint %}

Now you are done.


---

# 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://help.cerby.com/developer-tools/cerby-api/view-the-details-of-an-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.