Developer Settings
From the API Keys screen you can create credentials and register webhook endpoints without writing a single request by hand. It is the in-app counterpart to the API Reference.
Creating a key
Click + New key, give it a name (for example Production), and choose an environment:
| Environment | Prefix | Scope |
|---|---|---|
| Live | hc_live_ |
Actual USDG and actual transfers |
| Test | hc_test_ |
Robinhood Chain testnet, with no real funds involved |
You will see the full key only once, immediately after it is created, so copy it before closing the panel. We store just a hash, which means nobody can recover the key afterward, ourselves included. If you lose it, revoke it and create a new one. That is not a flaw; it is exactly how secure key handling should work.
Revoking a key
Clicking Revoke next to an active key disables it immediately and permanently, and any request that uses it afterward will fail. Revoked keys stay in the list with a Revoked label so your audit history remains complete.
Adding a webhook
Under Webhooks, + Add endpoint prompts you for:
- An HTTPS URL that will receive deliveries
- Which events to subscribe to:
transfer.settled,transfer.failed,payment.received,policy.limit_reached
Each endpoint receives only the event types you select. You can add as many endpoints as your consumers require (one forwarding to Slack, another feeding a billing system, and so on), each subscribed to its own set.
Managing endpoints
You can switch any endpoint between Active and Inactive, or delete it. Setting it to inactive pauses deliveries but keeps its configuration, which is handy while you fix the receiving side. Deleting it removes it permanently.
Event and payload reference
This screen handles keys and endpoints and nothing more. For the list of events, payload formats, and signature verification, see Real-Time Event Stream and the Webhooks API.