Create Your First Endpoint
An endpoint is your gateway to a blockchain network. Each endpoint includes:
- An HTTPS RPC URL for standard calls
- A WSS URL for WebSocket subscriptions
- A unique API Key
Steps
1. Navigate to Endpoints
From the Dashboard, click Endpoints in the left sidebar (or visit /dashboard/endpoint).
2. Click "Add Endpoint"
Click the + Add Endpoint button in the top right corner.
3. Select a Blockchain
Choose from the available networks:
| Network | Chain ID | Slug | Features |
|---|---|---|---|
| Ethereum | 1 | ethereum-rpc | Full; archive verification varies |
| Base | 8453 | base-rpc | Full; archive verification varies |
| BSC | 56 | bsc-rpc | Full; archive verification varies |
| Arbitrum One | 42161 | arbitrum-one-rpc | Full; archive verification varies |
| Polygon | 137 | polygon-bor-rpc | Keyed archive; public trial is restricted |
4. Name Your Endpoint (Optional)
Give your endpoint a descriptive name, e.g., "My DeFi Bot" or "Production Backend".
5. Choose Transaction Broadcasting (Ethereum, BSC and Base mainnet)
On Ethereum mainnet, BSC mainnet and Base mainnet, the dialog shows a Transaction Broadcasting setting. It controls how the endpoint sends your signed transactions (eth_sendRawTransaction):
- MEV Protection (default): sends your transactions privately to block builders so they cannot be front-run or sandwiched.
- Normal: broadcasts through our nodes to the public mempool. No private routing, no backruns and no rebates.
MEV Protection is selected by default. You can change the mode later with the broadcast icon in the endpoint list, or with the txBroadcast field of the Management API. Other EVM networks (such as Polygon) show it greyed out until they are supported; non-EVM networks don't show it.
6. Start Using Your Endpoint
After creation, you'll see your RPC URLs:
HTTPS: https://ethereum-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000
WSS: wss://ethereum-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000The public trial URL /v1/rpc/public takes no key: a request to it that also carries an X-API-Key or Authorization header, a cookie, or a key in the query is refused with 401. Send a key only to your own /v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000 URL.
Example Usage
curl -X POST https://ethereum-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000 \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Crypto API endpoint
To use the On-chain DEX API (DEX prices, pools, candles and trades) or the Wallet API, choose the Crypto API card in step 3. It creates an endpoint with the URL https://api.blockreq.com/v1/dex and a dedicated key that you send in the X-API-Key header. That key works only for /v1/dex, not for RPC, and the endpoint has no WSS URL or RPC tester.
Built-in RPC Tester
Each endpoint includes a built-in RPC tester. Click the Test button to open it, select an RPC method, and run it directly from your browser.