API ReferenceUtilities

Send Solana Transaction

Use Coinflow’s battle tested ⚔️ Transaction Sending (The same system we use to send our own transactions).

This endpoint sends a fully signed Solana transaction with retries and stable RPC servers. This is helpful during periods of network instability where the solution is to use better private RPC servers, retry transactions multiple times.

Authentication

Authorizationstring
The API key of the merchant - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key

Request

This endpoint expects an object.
transactionstringRequired
Base 58 encoded Solana Transaction. Supports Transctions and VersionedTransactions. Transaction must be signed by all signers.
confirmbooleanOptional

(Default: false)

Solana transactions after submission need to be confirmed as having been picked up by the network. State such as balance changes will not reflect until the transaction has been confirmed. Additionally, errors such as invalid signers, insufficient gas, and network congestion can lead to the transaction being dropped.

The most ideal solution to this is for you to implement your own client side confirmation logic with the Solana SDK, however we understand that is complex and not every merchant wants to do that.

Setting this property to true will mean the call will not return with your signature, until the solana transaction has been confirmed. If the transaction is unable to be confirmed by the time the blockhash expires, then you wil receive a 503 error.

Response

Ok
signaturestring

To confirm that this transaction was successful call connection.confirmTransaction(signature) which will query the chain to see if the transaction was confirmed.

Errors

412
Precondition Failed Error
417
Expectation Failed Error
503
Service Unavailable Error