> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/api-documentation/tutorials/reporting-api/manage-reporting-api-keys.md).

# Manage Reporting API Keys

The Reporting API Key management page lists all the existing keys on your workspace.

### Suspend reporting API keys

1. You can suspend and unsuspend a reporting API key at any time with **immediate effect** . This does not require the creation of a request to be approved by the admin quorum.

<figure><img src="/files/3ZlYQ7LcaK6UgomgZbRV" alt=""><figcaption></figcaption></figure>

### Revoke reporting API keys

2. You can request the revocation of a reporting API key. Admin approvers will be notified that a reporting API Key revocation request requires their approval. The API key will be suspended during the request approval process.

### Edit reporting API keys

3. You can edit the name and authorized entities of a reporting API key. Admin approvers will be notified that a reporting API key edition request requires their approval.


---

# 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.enterprise.ledger.com/api-documentation/tutorials/reporting-api/manage-reporting-api-keys.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.