---
title: "Broadcast signed Algorand transaction"
method: POST
path: "/v3/algorand/broadcast"
tags: ["Algorand - Tatum API"]
---

# Broadcast signed Algorand transaction

`POST /v3/algorand/broadcast`

<h4>2 credits per API call.</h4><br/>
<p>Broadcast signed transaction to Algorand blockchain. This method is used internally from Tatum KMS or Tatum client libraries.
It is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.</p>

## Request body

- BroadcastKMS
  - `txData` string, required — Raw signed transaction to be published to network.
  - `signatureId` string, uuid — ID of prepared payment template to sign. Required only, when broadcasting transaction signed by Tatum KMS.
  - `index` number — (Only if the signature ID is mnemonic-based and you run KMS v6.2 or later) The index of the address to send the assets from that was generated from the mnemonic

## Response `200`

OK

- AlgoTransactionHashKMS
  - `txId` string, required — TX hash of transaction.
  - `assetIndex` number — If transaction created new ASA asset, this value is the index of the asset on the network.
  - `confirmed` boolean — If transaction was not confirmed within 5 rounds, result is false.
  - `failed` boolean — In case of the transaction was broadcast to the blockchain, but it was not possible to complete Tatum KMS signature, reponse is marked as failed and must be marked manually.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `500` — Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.net/tatum/apis/blockchain-data.md) · [All operations](https://skmtc.net/tatum/apis/blockchain-data/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tatum/blockchain-data/versions/8622ee4b8fae/schema)