---
title: "BroadcastTx broadcast transaction."
method: POST
path: "/cosmos/tx/v1beta1/txs"
tags: ["Service"]
---

# BroadcastTx broadcast transaction.

`POST /cosmos/tx/v1beta1/txs`

## Request body

- CosmosTxV1beta1BroadcastTxRequest — BroadcastTxRequest is the request type for the Service.BroadcastTxRequest RPC method.
  - `tx_bytes` string, byte — tx_bytes is the raw transaction.
  - `mode` 'BROADCAST_MODE_UNSPECIFIED' | 'BROADCAST_MODE_BLOCK' | 'BROADCAST_MODE_SYNC' | 'BROADCAST_MODE_ASYNC' — BroadcastMode specifies the broadcast mode for the TxService.Broadcast RPC method. - BROADCAST_MODE_UNSPECIFIED: zero-value for mode ordering - BROADCAST_MODE_BLOCK: DEPRECATED: use BROADCAST_MODE_SYNC instead, BROADCAST_MODE_BLOCK is not supported by the SDK from v0.47.x onwards. - BROADCAST_MODE_SYNC: BROADCAST_MODE_SYNC defines a tx broadcasting mode where the client waits for a CheckTx execution response only. - BROADCAST_MODE_ASYNC: BROADCAST_MODE_ASYNC defines a tx broadcasting mode where the client returns immediately.

## Response `200`

A successful response.

- CosmosTxV1beta1BroadcastTxResponse — BroadcastTxResponse is the response type for the Service.BroadcastTx method.
  - `tx_response` CosmosBaseAbciV1beta1TxResponse — TxResponse defines a structure containing relevant tx data and metadata. The tags are stringified and the log is JSON decoded.
    - `height` string, int64
    - `txhash` string — The transaction hash.
    - `codespace` string
    - `code` integer — Response code.
    - `data` string — Result bytes, if any.
    - `raw_log` string — The output of the application's logger (raw string). May be non-deterministic.
    - `logs` CosmosBaseAbciV1beta1ABCIMessageLog[] — The output of the application's logger (typed). May be non-deterministic.
      - `msg_index` integer
      - `log` string
      - `events` CosmosBaseAbciV1beta1StringEvent[] — Events contains a slice of Event objects that were emitted during some execution.
        - `type` string
        - `attributes` CosmosBaseAbciV1beta1Attribute[]
          - `key` string
          - `value` string
    - `info` string — Additional information. May be non-deterministic.
    - `gas_wanted` string, int64 — Amount of gas requested for transaction.
    - `gas_used` string, int64 — Amount of gas consumed by transaction.
    - `tx` GoogleProtobufAny — `Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type. Example 1: Pack and unpack a message in C++. Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... } Example 2: Pack and unpack a message in Java. Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); } // or ... if (any.isSameTypeAs(Foo.getDefaultInstance())) { foo = any.unpack(Foo.getDefaultInstance()); } Example 3: Pack and unpack a message in Python. foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ... Example 4: Pack and unpack a message in Go foo := &pb.Foo{...} any, err := anypb.New(foo) if err != nil { ... } ... foo := &pb.Foo{} if err := any.UnmarshalTo(foo); err != nil { ... } The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z". JSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example: package google.profile; message Person { string first_name = 1; string last_name = 2; } { "@type": "type.googleapis.com/google.profile.Person", "firstName": <string>, "lastName": <string> } If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]): { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" }
      - `@type` string — A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.
    - `timestamp` string — Time of the previous block. For heights > 1, it's the weighted median of the timestamps of the valid votes in the block.LastCommit. For height == 1, it's genesis time.
    - `events` TendermintAbciEvent[] — Events defines all the events emitted by processing a transaction. Note, these events include those emitted by processing all the messages and those emitted from the ante. Whereas Logs contains the events, with additional metadata, emitted only by processing the messages. Since: cosmos-sdk 0.42.11, 0.44.5, 0.45
      - `type` string
      - `attributes` TendermintAbciEventAttribute[]
        - `key` string
        - `value` string
        - `index` boolean

## Other responses

- `default` — An unexpected error response.

---

[API](https://skmtc.net/coreumfoundation/apis/title-goes-here.md) · [All operations](https://skmtc.net/coreumfoundation/apis/title-goes-here/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/coreumfoundation/title-goes-here/revisions/2a2e5bc4593a/schema)