> For the complete documentation index, see [llms.txt](https://docs.hooded.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hooded.cash/using-hoodedcash/api-keys-and-webhooks.md).

# API Keys & Webhooks (Dashboard)

The API Keys page is where you generate credentials and configure webhook endpoints without writing a request by hand. It's the dashboard counterpart to the [API Reference](/api-reference/authentication.md).

***

## Generating a key

Click **+ New key**, give it a name (for example, `Production`), and choose an environment:

| Environment | Prefix     | Behavior                                         |
| ----------- | ---------- | ------------------------------------------------ |
| Live        | `hc_live_` | Real transfers against real USDG                 |
| Test        | `hc_test_` | Robinhood Chain testnet only, no real funds move |

The full key is shown exactly once, immediately after generation. Copy it before dismissing the panel — HoodedCash stores only a hash of it, so it cannot be shown to you again. If you lose it, revoke it and generate a new one.

***

## Revoking a key

Click **Revoke** next to any active key. Revocation is immediate and irreversible: the key stops authenticating on your very next request. Revoked keys stay listed, marked **Revoked**, for your own audit trail.

***

## Adding a webhook endpoint

Click **+ Add endpoint** under Webhooks, then provide:

* The HTTPS URL HoodedCash should deliver events to
* Which events it should receive: `transfer.settled`, `transfer.failed`, `payment.received`, `policy.limit_reached`

An endpoint only receives the event types you select. You can register multiple endpoints for different consumers (a Slack relay and your billing system, for example) with different event sets each.

***

## Managing endpoints

Each endpoint can be toggled **Active**/**Inactive** or removed entirely from the list. Deactivating pauses deliveries without losing the configuration, which is useful while debugging a receiving service; removing deletes it outright.

***

## Where to go for payload details

This page only covers key and endpoint management. For the event catalog, payload shapes, and signature verification, see [Webhooks & Events](/agents-and-automation/webhooks-and-events.md) and the [Webhooks API reference](/api-reference/webhooks.md).

***

## Next

* [Authentication](/api-reference/authentication.md)
* [Webhooks & Events](/agents-and-automation/webhooks-and-events.md)


---

# 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://docs.hooded.cash/using-hoodedcash/api-keys-and-webhooks.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.