Authorization

Each request to any Trader API endpoint should include your authorization header. For HTTP, gRPC, and WebSocket connections, your authorization should be included in the request headers. For QUIC/HTTP3 connections, your authorization is derived from your account's certificate over mTLS.

Obtaining an Auth Header

If you're an existing bloXroute customer, you can use the same authorization header as you would use for any other Cloud API offering from bloXroute.

If you are not a bloXroute customer, you can create an account and you can find your header from our account portal.

Using the header

You should include the authorization header upon establishing any connection with the Trader API.

HTTP

curl --header "Authorization: <YOUR-AUTHORIZATION-HEADER" https://ny.solana.dex.blxrbdn.com/api/v2/rate-limit

WebSocket

gRPC

QUIC

Client SDKs

By default, you can set the environment variable AUTH_HEADER to have our client SDKs automatically load the value for connections you make to the Trader API. You can also specify this manually –– consult each SDK's documentation for more details.