Build and sign
Prepare the instruction set, fees and recent blockhash. Sign the transaction in your application.
Solana transaction landing
Solana transaction landing.
From signed to submitted.
Send signed transactions to a regional Apex endpoint over JSON-RPC. Apex forwards them to the current leader and records how each transaction landed.
APEX / TRANSACTION DELIVERY
Your signed transaction
sendTransactionOrbitFlare ApexRegional endpointcurrent leader
LANDING RECORD
Signature
…transaction_signatureSlot
Recorded after landingLatency & tip
Delivery detailIllustrative transaction path. Delivery does not guarantee execution.
JSON-RPCUse familiar client code
RegionalChoose from 9 submission endpoints
Per transactionInspect the landing record
Follow the transaction
One path. Clear responsibilities.
Your application builds and signs the transaction. Apex handles the submission route and provides delivery visibility.
Submit to Apex
Send the signed payload with your API key to the appropriate regional JSON-RPC endpoint.
Inspect the result
Review the signature, slot, latency and tip recorded for the transaction. Your application still handles confirmation and retries.
Built for existing clients
Keep the interface you know.
Connect with standard sendTransaction code. Use your issued endpoint, API key and current integration settings.
app.ts
const signature = await connection.sendRawTransaction(
signedTransaction.serialize(),
{ skipPreflight: false }
);
// Track confirmation in your application.
// Use your issued Apex endpoint and API key.Example only · replace placeholders
Regional routing
Choose an endpoint close to your sending infrastructure.
Controlled access
API key access with an optional IP whitelist.
Delivery visibility
A landing record for understanding transaction submission.
Access and configuration
Start with your submission workload.
Apex access, capacity and configuration are confirmed by the team. Every API key starts at 5 TPS; ask for more when you request access.
ACCESS BY REQUEST
Request accessTell us what you are sending.
Share your preferred region (Frankfurt, Amsterdam, London, New York City, Salt Lake City, Singapore, Tokyo, Šiauliai, or Dublin), expected transaction rate and current submission path. We’ll help confirm the right integration.
Before you integrate
Submission is one part of the lifecycle.
Does Apex build or sign transactions?
No. Your application builds and signs the payload before sending it to Apex.
Does submission guarantee landing?
No transaction delivery service can guarantee execution of every transaction. Blockhash validity, fees, program errors and network conditions still matter.
Can I use existing JSON-RPC client code?
Apex uses standard JSON-RPC submission. Follow the integration settings supplied with your access and test your transaction path.
Is this a replacement for RPC reads?
Apex is a transaction delivery service. Use RPC for reads and simulation, and gRPC or Shredstream for your data feed.
Code. Build. Stream. Without Limits.
Give your transactions a dedicated route.
Talk through your region, capacity and integration requirements.