Endpoints - Sodae

Amsterdam

Service	Plaintext	TLS	Protocol
RPC	`http://ams.rpc.sodae.io:8899`	`https://ams.tls.sodae.io:443`	JSON-RPC 2.0, HTTP `POST`
Yellowstone gRPC	`http://ams.rpc.sodae.io:10201`	`https://ams.tls.sodae.io:443`	gRPC over HTTP/2
Preplay Shreds	`http://ams.rpc.sodae.io:10301`	`https://ams.tls.sodae.io:10311`	gRPC over HTTP/2
Price Feeds	`http://ams.feeds.sodae.io:10401`	`https://ams.feeds.sodae.io:443`	gRPC over HTTP/2

Both serve the same data with the same key. Plaintext has the lowest latency; TLS encrypts your key and traffic in transit and adds a handshake each time a connection opens. On the plaintext gRPC ports, configure your client for an insecure (non-TLS) channel:

GeyserGrpcClient::build_from_shared("http://ams.rpc.sodae.io:10201")?

new Client("http://ams.rpc.sodae.io:10201", token, {});

grpc.NewClient("ams.rpc.sodae.io:10201",
    grpc.WithTransportCredentials(insecure.NewCredentials()))

Over TLS, use the https:// URL and enable TLS:

GeyserGrpcClient::build_from_shared("https://ams.tls.sodae.io:443")?
    .tls_config(ClientTlsConfig::new().with_native_roots())?

new Client("https://ams.tls.sodae.io:443", token, {});

grpc.NewClient("ams.tls.sodae.io:443",
    grpc.WithTransportCredentials(credentials.NewTLS(&tls.Config{})))

In Rust, tonic 0.14 needs the tls-ring feature next to tls-native-roots, or the client panics when it opens a TLS connection. SodaStream delivers to your server rather than through a public endpoint.

Choosing a location

Place your servers in or near Amsterdam for the lowest latency. The endpoints are the same for every plan; what you can use depends on your plan and bound IPs.

WebSocket

RPC does not offer WebSocket subscriptions. For real-time data, use Yellowstone gRPC, which covers account, transaction and slot updates with server-side filtering. For live prices, use the Price Feeds gRPC streams.