For the complete documentation index, see llms.txt. This page is also available as Markdown.

API v2

High-performance transaction submission with reduced overhead.

A faster alternative to JSON-RPC that eliminates JSON parsing overhead and CORS preflight latency. Recommended for browser clients and performance-sensitive backends.

Request

Field
Value

Method

POST

Path

/api/sendTransaction2?c=<YOUR_API_KEY>

Content-Type

text/plain

Body

Base64-encoded transaction bytes

The body must be base64. API v2 does not accept raw binary transaction bytes. If you want to submit raw binary, use Batch Send, which works for a single transaction too.

Response

Returns an empty body with 200 OK on success. Does not return a transaction signature. Compute and track the signature client-side before submitting, then verify landing on-chain or in the dashboard.

Why Use API v2

Advantage
Detail

No CORS preflight

Saves 50–100ms per request from browser clients

Faster encoding

Base64 is faster to encode/decode than base58

Smaller payload

No JSON wrapper, plain text body

Lower overhead

No JSON parsing on the server side

When to Use

Use API v2 when you don't need the transaction signature returned in the response, and want the lowest possible submission latency. Ideal for browser-based applications and high-frequency backends.

If you need a transaction signature in the response, use JSON-RPC instead.

Last updated