---
title: "Broadcast a signed Bitcoin transaction"
method: POST
path: "/v3/bitcoin/broadcast"
tags: ["Bitcoin - Tatum API"]
---

# Broadcast a signed Bitcoin transaction

`POST /v3/bitcoin/broadcast`

## Request

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

/v3/bitcoin/broadcast

**2 credits per API call**

Broadcasts a signed transaction to the Bitcoin blockchain. This method is used internally from Tatum KMS or Tatum Client Libraries. It is possible to create a custom signing mechanism and only use this method for broadcasting data to the blockchain.

## 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

- TransactionHash
  - `txId` string, required: The hash (ID) of the transaction

## 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 perform the required operation due to a 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)