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

# Broadcast signed Celo transaction

`POST /v3/celo/broadcast`

/v3/celo/broadcast

**2 credits per API call**

Broadcast signed transaction to Celo 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.

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