sendTransaction

POST

Submits a signed transaction to the cluster for processing.This method does not alter the transaction in any way; it relays the transaction created by clients to the node as-is.If the node's rpc service receives the transaction, this method immediately succeeds, without waiting for any confirmations. A successful response from this method does not guarantee the transaction is processed or confirmed by the cluster.While the rpc service will reasonably retry to submit it, the transaction could be rejected if transaction's recent_blockhash expires before it lands.Use getSignatureStatuses to ensure a transaction is processed and confirmed.Before submitting, the following preflight checks are performed:The transaction signatures are verifiedThe transaction is simulated against the bank slot specified by the preflight commitment. On failure an error will be returned. Preflight checks may be disabled if desired. It is recommended to specify the same commitment and preflight commitment to avoid confusing behavior.The returned signature is the first signature in the transaction, which is used to identify the transaction (transaction id). This identifier can be easily extracted from the transaction data before submission.

param[0]

signedTransactionHashstringrequired

Fully-signed Transaction, as encoded string.

param[1]

configurationObjectobjectrequired

encodingstring

Encoding used for the transaction data. Values: base58 (slow, DEPRECATED), or base64.

skipPreflightboolean

When true, skip the preflight transaction checks. Default: false.

preflightCommitmentstring

The commitment describes how finalized a block is at that point in time.

finalized - the node will query the most recent block confirmed by supermajority of the cluster as having reached maximum lockout, meaning the cluster has recognized this block as finalized
confirmed - the node will query the most recent block that has been voted on by supermajority of the cluster.
processed - the node will query its most recent block. Note that the block may still be skipped by the cluster.

maxRetriesinteger

Maximum number of times for the RPC node to retry sending the transaction to the leader. If this parameter not provided, the RPC node will retry the transaction until it is finalized or until the blockhash expires.

minContextSlotstring

The minimum slot that the request can be evaluated at.

Responses

idinteger

The request ID

jsonrpcstring

The JSON-RPC version

resultinteger

The minimum ledger slot number

codestringrequired

Code identifying the cause of the failed request.

messagestringrequired

Detailed message including the name and value of the invalid parameter.

{
  "code": "ERROR_CODE",
  "message": "Bad Request"
}

X-API-KEY

cURL

curl -X POST 'https://solana-mainnet.nodit.io' \
  -H 'Content-Type: application/json' \
  -H 'X-API-KEY: nodit-demo' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendTransaction",
    "params": [
      "4hXTCkRzt9WyecNzV1XPgCDfGAZzQKNxLXgynz5QDuWWPSAZBZSHptvWRL3BjCvzUXRdKvHL2b7yGrRQcWyaqsaBCncVG7BFggS8w9snUts67BSh3EqKpXLUm5UMHfD7ZBe9GhARjbNQMLJ1QD3Spr6oMTBU6EhdB4RD8CP2xUxr2u3d6fos36PD98XS6oX8TQjLpsMwncs5DAMiD4nNnR8NBfyghGCWvCVifVwvA8B8TJxE1aiyiv2L429BCWfyzAme5sZW8rDb14NeCQHhZbtNqfXhcp2tAnaAT",
      {
        "encoding": "base58",
        "preflightCommitment": "processed"
      }
    ]
  }'