gearsAPI Documentation

The general API documentation for the RPC nodes and End Points provided by Syncnode

SyncNode API Documentation

Welcome to the official API documentation for SyncNode — public RPC endpoints for blockchain networks.

SyncNode provides reliable, rate-limited access to blockchain nodes over HTTPS and WebSocket. Whether you're building a dApp, monitoring on-chain activity, or integrating blockchain data into your backend, our RPC endpoints give you direct access to the networks you need.


Available Networks

Solana (Testnet)

A fully synced Solana testnet validator node exposing the standard JSON-RPC 2.0 API.

Property
Value

Endpoint

https://solanatds.syncnode.tech

Network

Solana Testnet

Protocol

JSON-RPC 2.0

Transport

HTTPS

Rate Limit

5 requests per 10 seconds per IP

Bellow some examples:

curl -X POST https://solanatds.syncnode.tech \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getHealth"}'

View Solana API Reference →


Ethereum (Mainnet Archive)

A Geth archive node on Ethereum mainnet with full historical state. Supports both HTTPS and WebSocket connections.

Property
Value

HTTP Endpoint

https://etharchive.syncnode.tech

WebSocket Endpoint

wss://etharchive.syncnode.tech/ws

Network

Ethereum Mainnet

Protocol

JSON-RPC 2.0

Transport

HTTPS / WSS

HTTP Rate Limit

30 requests per minute per IP

WebSocket

30 messages per minute, 60s max session

View bellow some examples:

View Ethereum API Reference →


General Information

Authentication

SyncNode endpoints are open and free to use — no API key or authentication is required. Rate limits are enforced per IP address to ensure fair access for everyone.

Protocol

All endpoints use the JSON-RPC 2.0 protocol. Requests must be sent as POST with Content-Type: application/json. GET requests are not supported and will return 405 Method Not Allowed.

Request format:

Response format:

Rate Limits

Each endpoint enforces per-IP rate limits. When you exceed the limit, the server responds with HTTP 429 Too Many Requests. Wait for the block duration to expire before retrying.

Network
HTTP Limit
Block Duration
WebSocket

Solana Testnet

5 req / 10s

10 seconds

N/A

Ethereum Mainnet

30 req / min

10 seconds

30 msg/min, 60s max session

Implement exponential backoff in your retry logic to handle rate limits gracefully.

Best Practices

  • Batch where possible. Both Solana and Ethereum support batching multiple calls in a single request to reduce your rate limit usage.

  • Cache slowly-changing data. Blockhashes, chain IDs, and epoch information don't change frequently — cache them for 30+ seconds.

  • Use the right commitment/finality. On Solana, use "confirmed" for speed or "finalized" for certainty. On Ethereum, specify block tags like "latest" or "finalized" based on your needs.

  • Handle errors. Always check for JSON-RPC error responses and HTTP status codes in your integration.

  • Use WebSocket for subscriptions. For Ethereum real-time data (new blocks, pending transactions), connect via wss://etharchive.syncnode.tech/ws instead of polling the HTTP endpoint.


Support

For questions, issues, or feature requests, reach out to the SyncNode team.

This documentation is continuously updated as new networks and methods become available.

Last updated