> 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

This article describes how to view the details of an active 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 %}

As a workspace **Owner**, **Super Admin**, or **Admin**, or as an API key **Owner**, you can view the details of an API key to check its configuration and usage.

{% hint style="info" %}
**NOTE:** Cerby does not display the API key value because it is hashed on generation. You can view the key name, creation date, expiration date, and its assigned scopes. You can also [update its scopes](/developer-tools/cerby-api/update-the-scopes-of-an-api-key.md).
{% endhint %}

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

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

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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