Create endpoint

Description

POST /api/dashboard/endpoints creates (or reuses) an endpoint for the Management API Key owner on BlockReq Web.

Request

ItemValue
MethodPOST
URLhttps://blockreq.com/api/dashboard/endpoints
HeaderAuthorization: Bearer akv1_...
Body{ "chain": "ethereum", "name": "optional", "txBroadcast": "mev_protection" }

Use GET /api/dashboard/chains for supported chain values.

Body fields

FieldTypeRequiredDescription
chainstringYesNetwork to create the endpoint on, e.g. ethereum or bsc.
namestringNoDisplay name for the endpoint.
keyModeshared | dedicatedNoshared (default) reuses your shared API key; dedicated creates a key for this endpoint only.
txBroadcastmev_protection | normalNoTransaction broadcasting for eth_sendRawTransaction. Default mev_protection.

Transaction broadcasting

txBroadcast applies on Ethereum mainnet (ethereum), BSC mainnet (bsc) and Base mainnet (base):

  • 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.

On other networks only mev_protection is accepted; normal returns 400 with tx_broadcast_unsupported_chain. Any other value is a 400 validation error whose issue message is tx_broadcast_invalid. If the request reuses an existing shared endpoint on the same network, that endpoint keeps its current mode.

To change the mode of an existing endpoint, send PATCH /api/dashboard/endpoints with { "endpointId": "ep_...", "txBroadcast": "normal" }. Endpoint list and detail responses include the current txBroadcast.

Code

curl -X POST https://blockreq.com/api/dashboard/endpoints \ -H "Authorization: Bearer akv1_YOUR_MANAGEMENT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"chain":"ethereum","txBroadcast":"mev_protection"}'

Try It

POST /dashboard/endpoints

https://blockreq.com/api/dashboard/endpoints