Integration in three steps

Syncro Sender is designed for fast integration without an infrastructure rebuild in many common setups. The process typically involves three steps:

Step 1: Sign the transaction as usual. The client application constructs and signs the transaction exactly as it does today. No changes to key management or signing logic are needed.

Step 2: Add the required tip. Include a transfer instruction in the transaction directing the minimum tip amount to P2P.org's designated wallet address. For the public endpoint, the minimum tip is 0.0001 SOL per transaction.

Step 3: Submit to the Syncro Sender endpoint. Send the signed transaction to the Syncro Sender REST endpoint using a standard sendTransaction JSON-RPC call. Syncro Sender handles multi-path routing from there.

Two access modes

Public endpoint: no API key required. Include the tip in the transaction and submit. This mode is available immediately for testing and evaluation, with a rate limit of 1 request per second.

Private (dedicated) endpoint: authenticated with an API key. Provides higher throughput (up to 50 RPS), dedicated infrastructure, and the ability to use the endpoint for both transaction submission and RPC read operations (getBalance, getAccountInfo, etc.) through a single connection.

API format

Syncro Sender accepts standard Solana JSON-RPC sendTransaction requests over REST. A typical integration involves replacing or augmenting the existing RPC endpoint URL with the Syncro Sender endpoint URL. Most teams add Syncro Sender as an additional submission endpoint alongside their existing infrastructure.

Time to integration

Teams may complete integration quickly (often within ~30 minutes) depending on their stack and review process. Since Syncro Sender accepts the same sendTransaction format used by standard Solana RPC nodes, the only modifications are typically the endpoint URL and the tip instruction.

Documentation

Full API documentation, including endpoint URLs, request and response formats, error codes, and code examples, is available at the developer documentation portal.

This article is for informational purposes only and does not constitute a service agreement. Use of Syncro Sender is governed by the Terms of Service: https://www.p2p.org/syncro-terms