Examples

Use the examples section based on the transport and level of control you need:

• HTTP: simplest way to integrate from any language using REST requests

• gRPC: recommended general-purpose integration if you want the full submission feature set

• QUIC: lowest-latency submission path for advanced traders sending raw signed transaction bytes

• TX Stream: separate real-time monitoring service for transaction streams, not a submission API

Which Path Should You Choose?

• Start with HTTP if you want the quickest integration and are fine working with JSON requests.

• Use gRPC if you want language-native clients and support for submission options such as front-running protection, revert-on-fail, disable-retries, and bundle submission.

• Use QUIC if latency is your top priority and you only need to send raw signed transaction bytes. QUIC does not support the extra gRPC submission flags or the batch submission endpoint.

• Use TX Stream if you want to monitor live transactions for trading or analytics. It uses a different authentication model from the main API.

Language Sections

• Golang

• Rust

• Python

• JavaScript/TypeScript

• HTTP