Send Methods

Pick the method that best fits your infrastructure and latency needs.

Method Comparison#

Method	Latency	Best For
JSON-RPC	Low	Drop-in replacement for your current RPC provider
HTTP Plaintext	Lower	Lightweight setups that skip JSON-RPC framing overhead
HTTP Binary	Lower	Pipelines that operate on raw serialized bytes

JSON-RPC#

The standard sendTransaction method ideal when you're moving from another RPC provider and want a drop-in replacement.

Request Format#

curl -sS 'http://$REGION.landing.fast' \
  -H 'Content-Type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendTransaction",
    "params": [
      "$BASE64_ENCODED_TX",
      {
        "encoding": "base64",
        "skipPreflight": true
      }
    ]
  }'

Response#

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "ewfUVUoisbalsSIGNATURE"
}

Recommended Parameters#

Parameter	Value	Reason
encoding	"base64"	Required for reliable transmission
skipPreflight	true	Preflight simulation is not supported

---

HTTP Plaintext#

http://<endpoint>.landing.fast/plaintext

Submits a base64-encoded transaction as plain text, bypassing the JSON-RPC wrapper. Carries less overhead than a standard RPC call.

Use Cases#

• Quick prototyping and ad-hoc testing
• Scripting and lightweight automation
• Cutting out JSON-RPC overhead

Request options#

Header	Value
Content-Type	text/plain
Body	Base64-encoded transaction string
Size	Up to 2048 bytes

Example#

curl -sS 'http://$ENDPOINT.landing.fast/plaintext' \
  -X POST \
  -H 'Content-Type: text/plain' \
  --data 'AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAQABAwIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQECAAAMAgAAAADh9QUAAAAAA=='

Response#

Plain-text bs58-encoded transaction signature:

Iod9csdlknmkdcmndcmdpc87...knmkdcmn

HTTP Binary#

http://<endpoint>.landing.fast/binary

Submits raw transaction bytes directly, eliminating base64 encoding overhead.

Use Cases#

• Workloads where every microsecond matters
• Trading systems that already handle raw transaction bytes
• Native pipelines built on bincode serialization

---

Request options#

Header	Value
Content-Type	application/octet-stream
Body	Raw transaction bytes (bincode serialized)
Size	Up to 1232 bytes

Example#

# Submit raw transaction bytes
curl -sS 'http://$ENDPOINT.landing.fast/binary' \
  -X POST \
  --data-binary @transaction.bin

Response#

Plain-text bs58-encoded transaction signature:

5wHu1qwD7q4a7vxK8rM3xP9jE2nL6sT8cR4hY7fZ1nD9...