---
title: "Broadcast and confirm signed Solana transaction"
method: POST
path: "/v3/solana/broadcast/confirm"
tags: ["Solana - Tatum API"]
---

# Broadcast and confirm signed Solana transaction

`POST /v3/solana/broadcast/confirm`

## Request

- Base URL: `https://api.tatum.io`
- URL: `https://api.tatum.io/v3/solana/broadcast/confirm`
- Auth: API key in header `x-api-key`

/v3/solana/broadcast/confirm

#### 10 credits per API call.

  

Broadcast signed custom transactions to Solana blockchain and waits for transaction confirmation depending on the commitment given. More information about commitment levels [here](https://docs.solana.com/ru/developing/clients/jsonrpc-api#configuring-state-commitment)

## Request body

- SolanaBroadcastConfirm
  - `txData` string, required: Raw signed transaction to be published to network.
  - `options` SolanaBroadcastConfirmOptions: Options for sending and waiting for a transaction
    - `commitment` 'confirmed' | 'finalized': Commitment to waiting for transaction confirmation
    - `preflightCommitment` 'confirmed' | 'finalized' | 'processed' | 'recent' | 'single' | 'singleGossip' | 'max': Preflight Commitment.

## Response `200`

OK

- SolanaTransactionHashWithConfirm
  - `txId` string, required: TX hash of successful transaction.
  - `confirmed` boolean, required: Indicates whether or not the transferred commitment has been fulfilled

## Other responses

- `400`: Bad Request
- `401`: Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `403`: Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.
- `500`: Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.dev/tatum/apis/blockchain.md) - [All operations](https://skmtc.dev/tatum/apis/blockchain/llms.txt) - [OpenAPI document](https://skmtc.dev/tatum/apis/blockchain/revisions/f9623a85f420?raw)