> ## Documentation Index > Fetch the complete documentation index at: https://cobo.com/developers/llms.txt > Use this file to discover all available pages before exploring further. # Get transaction receipt > This operation retrieves the receipt of a specified transaction on a specified EVM-compatible chain, which records the execution result of the transaction, including its status, block information, gas consumption, and the event logs emitted during execution. You need to specify the chain ID and the transaction hash. The chain ID can be retrieved by calling [List enabled chains](https://www.cobo.com/developers/v2/api-references/wallets/list-enabled-chains), and the transaction hash can be retrieved by calling [Get transaction information](https://www.cobo.com/developers/v2/api-references/transactions/get-transaction-information). The receipt is read from a blockchain node in real time and is returned as it is recorded on the chain. The event logs are returned in their raw form and are not filtered, so you need to decode them with the contract ABI yourself. This operation is applicable to EVM-compatible chains only. It currently supports `ETH` (Ethereum mainnet) and `SETH` (Ethereum Sepolia testnet) only. Requests for any other chain are rejected. You can only retrieve the receipts of the transactions under your organization. A receipt is available only after the transaction has been included in a block. If the transaction is still pending or does not exist on the specified chain, no receipt is returned. This operation is rate-limited to one request per second for each organization. Requests exceeding this limit will be rejected. Try [Cobo WaaS Skill](/developers/v2/guides/overview/cobo-waas-skill) in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster 🚀 ```python Python theme={null} import cobo_waas2 from cobo_waas2.models.transaction_receipt import TransactionReceipt from cobo_waas2.rest import ApiException from pprint import pprint # See configuration.py for a list of all supported configurations. configuration = cobo_waas2.Configuration( # Replace `` with your private key api_private_key="", # Select the development environment. To use the production environment, change the URL to https://api.cobo.com/v2. host="https://api.dev.cobo.com/v2", ) # Enter a context with an instance of the API client with cobo_waas2.ApiClient(configuration) as api_client: # Create an instance of the API class api_instance = cobo_waas2.TransactionsApi(api_client) chain_id = "ETH" tx_hash = "0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28" try: # Get transaction receipt api_response = api_instance.get_transaction_receipt(chain_id, tx_hash) print("The response of TransactionsApi->get_transaction_receipt:\n") pprint(api_response) except Exception as e: print("Exception when calling TransactionsApi->get_transaction_receipt: %s\n" % e) ``` ```java Java theme={null} // Import classes: import com.cobo.waas2.ApiClient; import com.cobo.waas2.ApiException; import com.cobo.waas2.Configuration; import com.cobo.waas2.Env; import com.cobo.waas2.api.TransactionsApi; import com.cobo.waas2.model.*; public class Example { public static void main(String[] args) { ApiClient defaultClient = Configuration.getDefaultApiClient(); // Select the development environment. To use the production environment, replace `Env.DEV` with // `Env.PROD defaultClient.setEnv(Env.DEV); // Replace `` with your private key defaultClient.setPrivKey(""); TransactionsApi apiInstance = new TransactionsApi(); String chainId = "ETH"; String txHash = "0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28"; try { TransactionReceipt result = apiInstance.getTransactionReceipt(chainId, txHash); System.out.println(result); } catch (ApiException e) { System.err.println("Exception when calling TransactionsApi#getTransactionReceipt"); System.err.println("Status code: " + e.getCode()); System.err.println("Reason: " + e.getResponseBody()); System.err.println("Response headers: " + e.getResponseHeaders()); e.printStackTrace(); } } } ``` ```go Go theme={null} package main import ( "context" "fmt" coboWaas2 "github.com/CoboGlobal/cobo-waas2-go-sdk/cobo_waas2" "github.com/CoboGlobal/cobo-waas2-go-sdk/cobo_waas2/crypto" "os" ) func main() { chainId := "ETH" txHash := "0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28" configuration := coboWaas2.NewConfiguration() // Initialize the API client apiClient := coboWaas2.NewAPIClient(configuration) ctx := context.Background() // Select the development environment. To use the production environment, replace coboWaas2.DevEnv with coboWaas2.ProdEnv ctx = context.WithValue(ctx, coboWaas2.ContextEnv, coboWaas2.DevEnv) // Replace `` with your private key ctx = context.WithValue(ctx, coboWaas2.ContextPortalSigner, crypto.Ed25519Signer{ Secret: "", }) resp, r, err := apiClient.TransactionsAPI.GetTransactionReceipt(ctx, chainId, txHash).Execute() if err != nil { fmt.Fprintf( os.Stderr, "Error when calling `TransactionsAPI.GetTransactionReceipt``: %v\n", err, ) fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r) } // response from `GetTransactionReceipt`: TransactionReceipt fmt.Fprintf(os.Stdout, "Response from `TransactionsAPI.GetTransactionReceipt`: %v\n", resp) } ``` ```javascript JavaScript theme={null} const CoboWaas2 = require("@cobo/cobo-waas2"); // Initialize the API client const apiClient = CoboWaas2.ApiClient.instance; // Select the development environment. To use the production environment, replace `Env.DEV` with `Env.PROD` apiClient.setEnv(CoboWaas2.Env.DEV); // Replace `` with your private key apiClient.setPrivateKey(""); // Call the API const apiInstance = new CoboWaas2.TransactionsApi(); const chain_id = "ETH"; const tx_hash = "0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28"; apiInstance.getTransactionReceipt(chain_id, tx_hash).then( (data) => { console.log("API called successfully. Returned data: " + data); }, (error) => { console.error(error); }, ); ``` ## OpenAPI ````yaml get /transactions/chains/{chain_id}/tx_hash/{tx_hash}/receipt openapi: 3.0.3 info: title: Cobo Wallet as a Service 2.0 description: > The Cobo Wallet-as-a-Service (WaaS) 2.0 API is the latest version of Cobo's WaaS API offering. It enables you to access Cobo's full suite of crypto wallet technologies with powerful and flexible access controls. By encapsulating complex security protocols and streamlining blockchain interactions, this API allows you to concentrate on your core business activities without worrying about the safety of your assets. The WaaS 2.0 API presents the following key features: - A unified API for Cobo's [all wallet types](https://manuals.cobo.com/en/portal/introduction#an-all-in-one-wallet-platform) - Support for 80+ chains and 3000+ tokens - A comprehensive selection of webhook events - Flexible usage models for MPC Wallets, including [Organization-Controlled Wallets](https://manuals.cobo.com/en/portal/mpc-wallets/ocw/introduction) and [User-Controlled Wallets](https://manuals.cobo.com/en/portal/mpc-wallets/ucw/introduction) - Seamlessly transfer funds across multiple exchanges, including Binance, OKX, Bybit, Deribit, and more For more information about the WaaS 2.0 API, see [Introduction to WaaS 2.0](https://www.cobo.com/developers/v2/guides/overview/introduction). termsOfService: https://cobo.com/waas/tos/ license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html contact: name: Cobo WaaS url: https://www.cobo.com/waas email: help@cobo.com version: 1.0.0 servers: - url: https://api.dev.cobo.com/v2 description: Development environment - url: https://api.cobo.com/v2 description: Production environment security: - CoboAuth: [] tags: - name: Organizations description: Operations related to Organizations. - name: Wallets description: Operations related to all wallets. - name: Wallets - MPC Wallets description: Operations related to mpc wallet. - name: Wallets - Exchange Wallet description: Operations related to exchange wallet. - name: Transactions description: Operations related to all transactions. - name: Developers - Webhooks description: Operations related to webhooks. - name: Stakings description: Operations related to staking. - name: OAuth description: Operations related to OAuth. - name: Developers description: Operations related to developers. - name: AddressBooks description: Operations related to address books. - name: TravelRule description: Operations related to travel rule. - name: GraphQL description: Operations related to executing GraphQL queries and mutations. - name: PrimeBroker description: Operations related to prime broker. - name: AppWorkflows description: Operations related to app workflow. - name: FeeStation description: Operations related to fee station. - name: Payment description: Operations related to payment. - name: Batch Payouts description: Operations related to batch payouts. - name: Tokenization description: Operations related to tokenization. - name: AutoSweep description: Operations related to auto sweep. - name: Compliance description: Operations related to compliance. - name: Reconciliation description: Operations related to reconciliation. - name: Internal - FeeEngine description: Internal operations related to fee engine . - name: Internal - Tokens description: Internal operations related to tokens. - name: Internal - Package description: Internal operations related to package management. paths: /transactions/chains/{chain_id}/tx_hash/{tx_hash}/receipt: parameters: - name: chain_id in: path required: true description: > The chain ID, which is the unique identifier of a blockchain. You can retrieve the IDs of all the chains you can use by calling [List enabled chains](https://www.cobo.com/developers/v2/api-references/wallets/list-enabled-chains). This operation currently supports the following chains only: - `ETH`: Ethereum mainnet. - `SETH`: Ethereum Sepolia testnet. schema: type: string example: ETH - name: tx_hash in: path required: true description: > The transaction hash, which is the unique identifier of a transaction on the blockchain. You can retrieve the transaction hash of a transaction by calling [Get transaction information](https://www.cobo.com/developers/v2/api-references/transactions/get-transaction-information). You need to specify the hash with the `0x` prefix. schema: type: string example: '0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28' get: tags: - Transactions summary: Get transaction receipt description: > This operation retrieves the receipt of a specified transaction on a specified EVM-compatible chain, which records the execution result of the transaction, including its status, block information, gas consumption, and the event logs emitted during execution. You need to specify the chain ID and the transaction hash. The chain ID can be retrieved by calling [List enabled chains](https://www.cobo.com/developers/v2/api-references/wallets/list-enabled-chains), and the transaction hash can be retrieved by calling [Get transaction information](https://www.cobo.com/developers/v2/api-references/transactions/get-transaction-information). The receipt is read from a blockchain node in real time and is returned as it is recorded on the chain. The event logs are returned in their raw form and are not filtered, so you need to decode them with the contract ABI yourself. This operation is applicable to EVM-compatible chains only. It currently supports `ETH` (Ethereum mainnet) and `SETH` (Ethereum Sepolia testnet) only. Requests for any other chain are rejected. You can only retrieve the receipts of the transactions under your organization. A receipt is available only after the transaction has been included in a block. If the transaction is still pending or does not exist on the specified chain, no receipt is returned. This operation is rate-limited to one request per second for each organization. Requests exceeding this limit will be rejected. operationId: get_transaction_receipt responses: '200': description: The information about a transaction receipt. content: application/json: schema: $ref: '#/components/schemas/TransactionReceipt' 4XX: $ref: '#/components/responses/badRequestError' 5XX: $ref: '#/components/responses/internalServerError' security: - CoboAuth: [] - OAuth2: - transaction.read components: schemas: TransactionReceipt: type: object description: > The information about a transaction receipt, which records the execution result of a transaction that has been included in a block. All the numeric properties are returned as decimal values instead of the hexadecimal values used by the JSON-RPC interfaces of the chains. The properties that record on-chain amounts are returned as strings to avoid any precision loss. required: - chain_id - transaction_hash - status - block_number - block_hash - transaction_index - from_address - gas_used - logs - logs_truncated properties: chain_id: type: string description: >- The chain ID, which is the unique identifier of a blockchain. You can retrieve the IDs of all the chains you can use by calling [List enabled chains](https://www.cobo.com/developers/v2/api-references/wallets/list-enabled-chains). example: ETH transaction_hash: type: string description: The transaction hash, returned with the `0x` prefix. example: '0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28' status: type: integer format: int32 description: > The execution result of the transaction. - `1`: The transaction was executed successfully. - `0`: The transaction failed, for example, because it was reverted by the contract or ran out of gas. example: 1 block_number: type: integer format: int64 description: The number of the block that contains the transaction. example: 20123456 block_hash: type: string description: The hash of the block that contains the transaction. example: '0xc9ee947f8bb6027c161888bf0d004bec05e7c2beec7e6b187dc512174e438735' transaction_index: type: integer format: int64 description: The index position of the transaction within the block. example: 42 from_address: type: string description: The address that sent the transaction. example: '0x1234567890abcdef1234567890abcdef12345678' to_address: type: string nullable: true description: >- The address that received the transaction. The value is `null` if the transaction created a contract. example: '0xdac17f958d2ee523a2206206994597c13d831ec7' contract_address: type: string nullable: true description: >- The address of the contract created by the transaction. The value is `null` if the transaction did not create a contract. example: '0xabcdef1234567890abcdef1234567890abcdef12' gas_used: type: string description: The number of gas units consumed by the transaction. example: '21000' cumulative_gas_used: type: string description: >- The total number of gas units consumed by all the transactions up to and including this transaction in the block. example: '8000000' effective_gas_price: type: string description: >- The gas price actually paid for each gas unit consumed by the transaction, in the smallest unit of the chain's native token. For example, the value is in wei for Ethereum. example: '25000000000' evm_transaction_type: type: integer format: int32 description: > The transaction envelope type defined by the chain. This property describes the on-chain transaction format, not the Cobo transaction type returned by [Get transaction information](https://www.cobo.com/developers/v2/api-references/transactions/get-transaction-information). - `0`: A legacy transaction. - `1`: An access list transaction, as defined in EIP-2930. - `2`: A dynamic fee transaction, as defined in EIP-1559. example: 2 logs_bloom: type: string description: >- The bloom filter of the event logs emitted during the execution of the transaction, which can be used to quickly check whether the transaction emitted a specific log. The value is a 256-byte hexadecimal string. example: >- 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 logs: type: array description: >- The event logs emitted during the execution of the transaction, in the order in which they were emitted. The array is empty if the transaction emitted no logs. A maximum of 1,000 logs are returned. If the transaction emitted more logs, only the first 1,000 are returned and `logs_truncated` is `true`. items: $ref: '#/components/schemas/TransactionReceiptLog' logs_truncated: type: boolean description: > Whether the event logs returned in `logs` were truncated. - `true`: The transaction emitted more than 1,000 logs and only the first 1,000 are returned. - `false`: All the logs emitted by the transaction are returned. example: false TransactionReceiptLog: type: object description: >- The information about an event log emitted during the execution of a transaction. required: - log_index - address - topics - data properties: log_index: type: integer format: int64 description: The index position of the log within the block. example: 5 address: type: string description: The address of the contract that emitted the log. example: '0xdac17f958d2ee523a2206206994597c13d831ec7' topics: type: array description: >- The indexed log arguments. The first topic is the hash of the event signature, and the remaining topics are the indexed event parameters, with a maximum of three. items: type: string example: '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef' data: type: string description: The non-indexed log arguments, encoded as a hexadecimal string. example: '0x00000000000000000000000000000000000000000000000000000000000f4240' block_number: type: integer format: int64 description: The number of the block that contains the log. example: 20123456 block_hash: type: string description: The hash of the block that contains the log. example: '0xc9ee947f8bb6027c161888bf0d004bec05e7c2beec7e6b187dc512174e438735' transaction_hash: type: string description: The hash of the transaction that emitted the log. example: '0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28' transaction_index: type: integer format: int64 description: >- The index position within the block of the transaction that emitted the log. example: 42 removed: type: boolean description: > Whether the log was removed due to a chain reorganization. - `true`: The log was removed because the block that contains it was reorganized out of the canonical chain. - `false`: The log is still valid. example: false ErrorResponse: type: object description: The response of a failed request. required: - error_code - error_message - error_id properties: error_code: type: integer description: >- The error code. Refer to [Error codes and status codes](https://www.cobo.com/developers/v2/api-references/error-codes) for more details. error_message: type: string description: The error description. error_id: type: string description: >- The error log ID. You can provide the error ID when submitting a ticket to help Cobo to locate the issue. example: 0b6ddf19083c4bd1a9ca01bec44b24dd responses: badRequestError: description: >- Bad request. Your request contains malformed syntax or invalid parameters. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' internalServerError: description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: CoboAuth: type: apiKey in: header name: BIZ-API-KEY description: > The API key. For more details, refer to [API key](https://www.cobo.com/developers/v2/guides/overview/cobo-auth#api-key). In the API playground, enter your [API secret](https://www.cobo.com/developers/v2/guides/overview/cobo-auth#api-secret), and your API key will be accordingly calculated. OAuth2: type: oauth2 description: >- The [Org Access Token](https://www.cobo.com/developers/v2/apps/org-access-tokens). Use this authorization method only if you are developing Cobo Portal Apps for installation and use across different organizations. flows: authorizationCode: authorizationUrl: https://auth.cobo.com/authorize tokenUrl: https://auth.cobo.com/oauth/token scopes: address_book.read: Read address book api_key.read: Read API key information callback.read: Read callback message callback.resend: Resend callback message wallet.create: Create wallet wallet.read: Read wallet information wallet.update: Update wallet information wallet.delete: Delete wallet information wallet.create_address: Create wallet address wallet.manage_utxo: Manage UTXO mpc_project.create: Create MPC project mpc_project.read: Read MPC project information mpc_project.update: Update MPC project information mpc_vault.create: Create MPC Vault mpc_vault.read: Read MPC Vault information mpc_vault.update: Update MPC Vault information mpc_key_group.create: Create MPC key group mpc_key_group.read: Read MPC key group information mpc_key_group.update: Update MPC key group information mpc_key_group.delete: Delete MPC key group information transaction.read: Read transaction information transaction.withdraw: Make withdrawals transaction.estimate_fee: Estimate transaction fee transaction.contract_call: Initiate contract calls transaction.message_sign: Initiate message signings transaction.stake: Stake assets transaction.unstake: Unstake assets transaction.unstake_withdraw: Withdraw unstaked assets transaction.manage: Manage ongoing transactions transaction.update: Update transaction notes travel_rule.read: Read travel rule information travel_rule.edit: Edit travel rule information webhook.read: Read webhook URLs/events webhook.edit: Edit webhook URLs webhook.resend: Resend webhook events payment_orders_payin.create: Create pay-in order payment_orders_payin.read: Read pay-in order information payment_orders_payin.update: Update pay-in order payment_orders_refund.create: Create payment refund order payment_orders_refund.read: Read payment refund order information payment_settlement.create: Create payment settlement request payment_settlement.read: Read payment settlement request information payment_merchant.create: Create payment merchant payment_merchant.read: Read payment merchant information payment_merchant.update: Update payment merchant payment_forced_sweep.create: Create payment force sweep request payment_forced_sweep.read: Read payment force sweep request information compliance_funds.refund: Refund compliance funds request compliance_funds.isolate: Isolate compliance funds request compliance_funds.unfreeze: Unfreeze compliance funds request compliance_funds.read: Read compliance funds request information compliance_kyt_review.update: Update KYT review status compliance_kyt_decisions.update: Update KYT decision status compliance_kyt_status.read: Read KYT screening status compliance_kya_screenings.create: Create KYA address screening requests compliance_kya_screenings.read: Read KYA address screening results ````