--- title: "GetTxsEvent fetches txs by event." method: GET path: "/cosmos/tx/v1beta1/txs" tags: ["Service"] --- # GetTxsEvent fetches txs by event. `GET /cosmos/tx/v1beta1/txs` ## Query parameters - `events` string[] - `pagination.key` string, byte - `pagination.offset` string, uint64 - `pagination.limit` string, uint64 - `pagination.count_total` boolean - `pagination.reverse` boolean - `order_by` 'ORDER_BY_UNSPECIFIED' | 'ORDER_BY_ASC' | 'ORDER_BY_DESC' - `page` string, uint64 - `limit` string, uint64 - `query` string ## Response `200` A successful response. - CosmosTxV1beta1GetTxsEventResponse — GetTxsEventResponse is the response type for the Service.TxsByEvents RPC method. - `pagination` CosmosBaseQueryV1beta1PageResponse — PageResponse is to be embedded in gRPC response messages where the corresponding request message has used PageRequest. message SomeResponse { repeated Bar results = 1; PageResponse page = 2; } - `next_key` string, byte — next_key is the key to be passed to PageRequest.key to query the next page most efficiently. It will be empty if there are no more results. - `total` string, uint64 - `total` string, uint64 - `tx_responses` CosmosBaseAbciV1beta1TxResponse[] — tx_responses is the list of queried TxResponses. - `code` integer — Response code. - `codespace` string - `data` string — Result bytes, if any. - `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. - `attributes` TendermintAbciEventAttribute[] - `index` boolean - `key` string - `value` string - `type` string - `gas_used` string, int64 — Amount of gas consumed by transaction. - `gas_wanted` string, int64 — Amount of gas requested for transaction. - `height` string, int64 - `info` string — Additional information. May be non-deterministic. - `logs` CosmosBaseAbciV1beta1ABCIMessageLog[] — The output of the application's logger (typed). May be non-deterministic. - `events` CosmosBaseAbciV1beta1StringEvent[] — Events contains a slice of Event objects that were emitted during some execution. - `attributes` CosmosBaseAbciV1beta1Attribute[] - `key` string - `value` string - `type` string - `log` string - `msg_index` integer - `raw_log` string — The output of the application's logger (raw string). May be non-deterministic. - `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. - `tx` GoogleProtobufAny - `@type` string - `txhash` string — The transaction hash. - `txs` CosmosTxV1beta1Tx[] — txs is the list of queried transactions. - `auth_info` CosmosTxV1beta1AuthInfo — AuthInfo describes the fee and signer modes that are used to sign a transaction. - `fee` CosmosTxV1beta1Fee — Fee includes the amount of coins paid in fees and the maximum gas to be used by the transaction. The ratio yields an effective "gasprice", which must be above some miminum to be accepted into the mempool. - `amount` CosmosBaseV1beta1Coin[] - `amount` string - `denom` string - `gas_limit` string, uint64 - `granter` string - `payer` string — if unset, the first signer is responsible for paying the fees. If set, the specified account must pay the fees. the payer must be a tx signer (and thus have signed this field in AuthInfo). setting this field does *not* change the ordering of required signers for the transaction. - `signer_infos` CosmosTxV1beta1SignerInfo[] — signer_infos defines the signing modes for the required signers. The number and order of elements must match the required signers from TxBody's messages. The first element is the primary signer and the one which pays the fee. - `mode_info` CosmosTxV1beta1ModeInfo — ModeInfo describes the signing mode of a single or nested multisig signer. - `multi` CosmosTxV1beta1ModeInfoMulti - `bitarray` CosmosCryptoMultisigV1beta1CompactBitArray — CompactBitArray is an implementation of a space efficient bit array. This is used to ensure that the encoded data takes up a minimal amount of space after proto encoding. This is not thread safe, and is not intended for concurrent usage. - … - `mode_infos` CosmosTxV1beta1ModeInfo[] - `single` CosmosTxV1beta1ModeInfoSingle - `mode` 'SIGN_MODE_UNSPECIFIED' | 'SIGN_MODE_DIRECT' | 'SIGN_MODE_TEXTUAL' | 'SIGN_MODE_DIRECT_AUX' | 'SIGN_MODE_LEGACY_AMINO_JSON' | 'SIGN_MODE_EIP_191' — SignMode represents a signing mode with its own security guarantees. This enum should be considered a registry of all known sign modes in the Cosmos ecosystem. Apps are not expected to support all known sign modes. Apps that would like to support custom sign modes are encouraged to open a small PR against this file to add a new case to this SignMode enum describing their sign mode so that different apps have a consistent version of this enum. - SIGN_MODE_UNSPECIFIED: SIGN_MODE_UNSPECIFIED specifies an unknown signing mode and will be rejected. - SIGN_MODE_DIRECT: SIGN_MODE_DIRECT specifies a signing mode which uses SignDoc and is verified with raw bytes from Tx. - SIGN_MODE_TEXTUAL: SIGN_MODE_TEXTUAL is a future signing mode that will verify some human-readable textual representation on top of the binary representation from SIGN_MODE_DIRECT. Since: cosmos-sdk 0.50 - SIGN_MODE_DIRECT_AUX: SIGN_MODE_DIRECT_AUX specifies a signing mode which uses SignDocDirectAux. As opposed to SIGN_MODE_DIRECT, this sign mode does not require signers signing over other signers' `signer_info`. Since: cosmos-sdk 0.46 - SIGN_MODE_LEGACY_AMINO_JSON: SIGN_MODE_LEGACY_AMINO_JSON is a backwards compatibility mode which uses Amino JSON and will be removed in the future. - SIGN_MODE_EIP_191: SIGN_MODE_EIP_191 specifies the sign mode for EIP 191 signing on the Cosmos SDK. Ref: https://eips.ethereum.org/EIPS/eip-191 Currently, SIGN_MODE_EIP_191 is registered as a SignMode enum variant, but is not implemented on the SDK by default. To enable EIP-191, you need to pass a custom `TxConfig` that has an implementation of `SignModeHandler` for EIP-191. The SDK may decide to fully support EIP-191 in the future. Since: cosmos-sdk 0.45.2 - `public_key` GoogleProtobufAny - `@type` string - `sequence` string, uint64 — sequence is the sequence of the account, which describes the number of committed transactions signed by a given address. It is used to prevent replay attacks. - `tip` CosmosTxV1beta1Tip — Tip is the tip used for meta-transactions. - `amount` CosmosBaseV1beta1Coin[] - `amount` string - `denom` string - `tipper` string - `body` CosmosTxV1beta1TxBody — TxBody is the body of a transaction that all signers sign over. - `extension_options` GoogleProtobufAny[] - `@type` string - `memo` string — memo is any arbitrary note/comment to be added to the transaction. WARNING: in clients, any publicly exposed text should not be called memo, but should be called `note` instead (see https://github.com/cosmos/cosmos-sdk/issues/9122). - `messages` GoogleProtobufAny[] — messages is a list of messages to be executed. The required signers of those messages define the number and order of elements in AuthInfo's signer_infos and Tx's signatures. Each required signer address is added to the list only the first time it occurs. By convention, the first required signer (usually from the first message) is referred to as the primary signer and pays the fee for the whole transaction. - `@type` string - `non_critical_extension_options` GoogleProtobufAny[] - `@type` string - `timeout_height` string, uint64 — timeout_height is the block height after which this transaction will not be processed by the chain. - `timeout_timestamp` string, date-time — timeout_timestamp is the block time after which this transaction will not be processed by the chain. Note, if unordered=true this value MUST be set and will act as a short-lived TTL in which the transaction is deemed valid and kept in memory to prevent duplicates. - `unordered` boolean — unordered, when set to true, indicates that the transaction signer(s) intend for the transaction to be evaluated and executed in an un-ordered fashion. Specifically, the account's nonce will NOT be checked or incremented, which allows for fire-and-forget as well as concurrent transaction execution. Note, when set to true, the existing 'timeout_timestamp' value must be set and will be used to correspond to a timestamp in which the transaction is deemed valid. When true, the sequence value MUST be 0, and any transaction with unordered=true and a non-zero sequence value will be rejected. External services that make assumptions about sequence values may need to be updated because of this. - `signatures` string[] — signatures is a list of signatures that matches the length and order of AuthInfo's signer_infos to allow connecting signature meta information like public key and signing mode by position. ## Other responses - `default` — An unexpected error response. ## Changes - **2025-05-21** `3874a03b0e7b` — 1 info - api operation id `UpgradeService_GetTxsEvent` removed and replaced with `EvidenceService_GetTxsEvent` - **2025-05-09** `8dbfaa2bebb2` — 1 info - api operation id `CircuitService_GetTxsEvent` removed and replaced with `UpgradeService_GetTxsEvent` - **2025-04-08** `21a675703a05` — 1 info - api operation id `AuthService_GetTxsEvent` removed and replaced with `CircuitService_GetTxsEvent` - **2025-03-27** `4f349536c8f3` — 1 info - api operation id `FeegrantService_GetTxsEvent` removed and replaced with `AuthService_GetTxsEvent` - **2025-02-24** `2ab9d24288c2` — 1 info - api operation id `CircuitService_GetTxsEvent` removed and replaced with `FeegrantService_GetTxsEvent` [Full history](https://skmtc.dev/pokt-network/apis/http-api-console/changes/cosmos/tx/v1beta1/txs/get.md) --- [API](https://skmtc.dev/pokt-network/apis/http-api-console.md) · [All operations](https://skmtc.dev/pokt-network/apis/http-api-console/llms.txt) · [OpenAPI document](https://skmtc.dev/pokt-network/apis/http-api-console/revisions/671fab54b729?raw)