---
title: "submitTransaction"
method: POST
path: "/construction/submit"
tags: ["Cardano - Rosetta"]
---

# submitTransaction

`POST /construction/submit`

Submit a pre-signed transaction to the node. This call should not block
on the transaction being included in a block. Rather, it should return
immediately with an indication of whether or not the transaction was
included in the mempool.

The transaction submission response should only return a 200 status
if the submitted transaction could be included in the mempool.
Otherwise, it should return an error.

## Request body

- ConstructionSubmitRequest — The transaction submission request includes a signed transaction.
  - `network_identifier` NetworkIdentifier, required — The network_identifier specifies which network a particular object is associated with.
    - `blockchain` string, required
    - `network` string, required — If a blockchain has a specific chain-id or network identifier, it should go in this field. It is up to the client to determine which network-specific identifier is mainnet or testnet.
    - `sub_network_identifier` SubNetworkIdentifier — In blockchains with sharded state, the SubNetworkIdentifier is required to query some object on a specific shard. This identifier is optional for all non-sharded blockchains.
      - `network` string, required
      - `metadata` object
  - `signed_transaction` string, required

## Response `200`

Expected response to a valid request

- TransactionIdentifierResponse — TransactionIdentifierResponse contains the transaction_identifier of a transaction that was submitted to either `/construction/hash` or `/construction/submit`.
  - `transaction_identifier` TransactionIdentifier, required — The transaction_identifier uniquely identifies a transaction in a particular network and block or in the mempool.
    - `hash` string, required — Any transactions that are attributable only to a block (ex: a block event) should use the hash of the block as the identifier. This should be normalized according to the case specified in the transaction_hash_case in network options.
  - `metadata` object

## Other responses

- `500` — unexpected error

---

[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)