> For the complete documentation index, see [llms.txt](https://docs.useglade.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useglade.org/guides-for-the-app/developer-tools.md).

# Tools for developers

The API Keys screen lets you issue credentials and set up webhook endpoints from inside the app, with no hand-written requests. Think of it as the point-and-click companion to the [authentication reference](/api-reference/authentication.md).

***

## Issuing an API key

1. Click **+ New key**.
2. Name it, for instance `Production`.
3. Pick the environment it belongs to.

| Environment | Key prefix | What it touches                           |
| ----------- | ---------- | ----------------------------------------- |
| Live        | `hc_live_` | Real USDG and real transfers              |
| Test        | `hc_test_` | Robinhood Chain testnet, so no real money |

The full key appears a single time, right after you create it. Copy it before you close the panel. Glade keeps only a hash of the key, so neither you nor we can retrieve it later. Lost a key? Revoke it and issue another. This is deliberate, and it's how keys should be handled.

***

## Revoking an API key

Press **Revoke** beside any active key. It stops working straight away and can't be reactivated; every request made with it from then on fails. The key remains in your list marked **Revoked**, which keeps your audit trail complete.

***

## Registering a webhook endpoint

In the Webhooks section, choose **+ Add endpoint** and supply:

* **A URL** using HTTPS, where deliveries will be sent
* **The events** you want: any of `transfer.settled`, `transfer.failed`, `payment.received` and `policy.limit_reached`

An endpoint only receives the event types you chose for it. There's no need to funnel everything through one endpoint. You can create as many as your systems need, say one that posts to Slack and another that feeds billing, each with its own event selection.

***

## Pausing or removing an endpoint

Each endpoint can be set to **Active** or **Inactive**, or deleted outright.

| Action          | Effect                                                                                          |
| --------------- | ----------------------------------------------------------------------------------------------- |
| Set to Inactive | Deliveries stop, but the configuration is kept. Useful while you repair whatever receives them. |
| Delete          | The endpoint is gone for good.                                                                  |

***

## Events and payloads

This screen is limited to managing keys and endpoints. The full event list, payload shapes and signature verification steps live in [Live events](/agents/live-events.md) and the [Webhooks API](/api-reference/webhooks-api.md).

***

## Related pages

* [Authentication](/api-reference/authentication.md)
* [Live events](/agents/live-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 by asking a question.

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

```
GET https://docs.useglade.org/guides-for-the-app/developer-tools.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.