Module aws_sdk_managedblockchainquery::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon Managed Blockchain Query can respond with.

Structs

• AssetContract

  This container contains information about an contract.

• BatchGetTokenBalanceErrorItem

  Error generated from a failed BatchGetTokenBalance request.

• BatchGetTokenBalanceInputItem

  The container for the input for getting a token balance.

• BatchGetTokenBalanceOutputItem

  The container for the properties of a token balance output.

• BlockchainInstant

  The container for time.

• ContractFilter

  The contract or wallet address by which to filter the request.

• ContractIdentifier

  Container for the blockchain address and network information about a contract.

• ContractMetadata

  The metadata of the contract.

• ListTransactionsSort

  The container for determining how the list transaction result will be sorted.

• OwnerFilter

  The container for the owner information to filter by.

• OwnerIdentifier

  The container for the identifier of the owner.

• TokenBalance

  The balance of the token.

• TokenFilter

  The container of the token filter like the contract address on a given blockchain network or a unique token identifier on a given blockchain network.

• TokenIdentifier

  The container for the identifier for the token including the unique token ID and its blockchain network.

• Transaction

  There are two possible types of transactions used for this data type:

• TransactionEvent

  The container for the properties of a transaction event.

• TransactionOutputItem

  The container of the transaction output.

• ValidationExceptionField

  The resource passed is invalid.

Enums

• ErrorType
  When writing a match expression against ErrorType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ListTransactionsSortBy
  When writing a match expression against ListTransactionsSortBy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• QueryNetwork
  When writing a match expression against QueryNetwork, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• QueryTokenStandard
  When writing a match expression against QueryTokenStandard, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• QueryTransactionEventType
  When writing a match expression against QueryTransactionEventType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• QueryTransactionStatus
  When writing a match expression against QueryTransactionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceType
  When writing a match expression against ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SortOrder
  When writing a match expression against SortOrder, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ValidationExceptionReason
  When writing a match expression against ValidationExceptionReason, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.