ListTransactionEvents
Lists all the transaction events for a transaction
Note
This action will return transaction details for all transactions that are confirmed on the blockchain, even if they have not reached finality.
Request Syntax
POST /list-transaction-events HTTP/1.1
Content-type: application/json
{
"maxResults": number
,
"network": "string
",
"nextToken": "string
",
"transactionHash": "string
",
"transactionId": "string
"
}
URI Request Parameters
The request does not use any URI parameters.
Request Body
The request accepts the following data in JSON format.
- maxResults
-
The maximum number of transaction events to list.
Default:
100
Note
Even if additional results can be retrieved, the request can return less results than
maxResults
or an empty array of results.To retrieve the next set of results, make another request with the returned
nextToken
value. The value ofnextToken
isnull
when there are no more results to returnType: Integer
Valid Range: Minimum value of 1. Maximum value of 250.
Required: No
- network
-
The blockchain network where the transaction events occurred.
Type: String
Valid Values:
ETHEREUM_MAINNET | ETHEREUM_SEPOLIA_TESTNET | BITCOIN_MAINNET | BITCOIN_TESTNET
Required: Yes
- nextToken
-
The pagination token that indicates the next set of results to retrieve.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 131070.
Required: No
- transactionHash
-
The hash of a transaction. It is generated when a transaction is created.
Type: String
Pattern:
(0x[A-Fa-f0-9]{64}|[A-Fa-f0-9]{64})
Required: No
- transactionId
-
The identifier of a Bitcoin transaction. It is generated when a transaction is created.
Note
transactionId
is only supported on the Bitcoin networks.Type: String
Pattern:
(0x[A-Fa-f0-9]{64}|[A-Fa-f0-9]{64})
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"events": [
{
"blockchainInstant": {
"time": number
},
"confirmationStatus": "string",
"contractAddress": "string",
"eventType": "string",
"from": "string",
"network": "string",
"spentVoutIndex": number,
"spentVoutTransactionHash": "string",
"spentVoutTransactionId": "string",
"to": "string",
"tokenId": "string",
"transactionHash": "string",
"transactionId": "string",
"value": "string",
"voutIndex": number,
"voutSpent": boolean
}
],
"nextToken": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- events
-
An array of
TransactionEvent
objects. Each object contains details about the transaction events.Type: Array of TransactionEvent objects
Array Members: Minimum number of 0 items. Maximum number of 250 items.
- nextToken
-
The pagination token that indicates the next set of results to retrieve.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 131070.
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
The AWS account doesn’t have access to this resource.
HTTP Status Code: 403
- InternalServerException
-
The request processing has failed because of an internal error in the service.
HTTP Status Code: 500
- ServiceQuotaExceededException
-
The service quota has been exceeded for this resource.
HTTP Status Code: 402
- ThrottlingException
-
The request or operation couldn't be performed because a service is throttling requests. The most common source of throttling errors is when you create resources that exceed your service limit for this resource type. Request a limit increase or delete unused resources, if possible.
HTTP Status Code: 429
- ValidationException
-
The resource passed is invalid.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: