Get a key
How to ask for a key, what a key does, and how to keep it safe.
Ask for a key
Email developers@blockhash.xyz. Name your project and what you need: the RPC, the Data API, or both. Say what load you expect. There is no self-serve sign-up.
What a key does
The RPC and the Data API take separate keys.
| RPC | Data API | |
|---|---|---|
| Key | Required | Optional |
| Where it goes | The last segment of the URL: https://robinhood-mainnet.rpc.blockhash.xyz/<key> | The header Authorization: Bearer <key> |
| Without a key | No access: the URL answers 404. | The public rate limits, counted by your client address. |
| With a key | The RPC's limits, counted for your key. | Higher rate limits, counted for your key. |
Keep it on your server
Anyone who holds your key uses your limits.
Call both products from your server, never from a browser or an app's bundle.
The Data API refuses a request that carries a key and an Origin header with 403 key-server-only.
The RPC key is part of its URL, so keep the whole URL out of client code, logs and public repositories.
If a key leaks, email developers@blockhash.xyz at once to have it revoked.
A revoked RPC key answers 404 within a second.
A revoked Data API key stops working within 30 seconds.