Find the metadata of the transaction.
GET/api/core/v3/transactions/:transactionId/metadata
Find the metadata of the transaction.
Request
Path Parameters
Identifier of the transaction to look up.
Responses
- 200
- 400
- 403
- 404
- 500
- 503
Successful operation.
- application/json
- Schema
- Example (from schema)
- default
Schema
1
- denotes that the referenced UTXO was already spent.2
- denotes that the transaction is conflicting with another transaction. Conflicting specifically means a double spend situation that both transaction pass all validation rules, eventually losing one(s) should have this reason.3
- denotes that the referenced UTXO is invalid.4
- denotes that the transaction is invalid.5
- denotes that the sum of the inputs and output base token amount does not match.6
- denotes that the unlock block signature is invalid.7
- denotes that the configured timelock is not yet expired.8
- denotes that the given native tokens are invalid.9
- denotes that the return amount in a transaction is not fulfilled by the output side.10
- denotes that the input unlock is invalid.11
- denotes that an output contains a Sender with an ident (address) which is not unlocked.12
- denotes that the chain state transition is invalid.13
- denotes that the referenced input is created after transaction issuing time.14
- denotes that the mana amount is invalid.15
- denotes that the Block Issuance Credits Input is invalid.16
- denotes that Reward Context Input is invalid.17
- denotes that Commitment Context Input is invalid.18
- denotes that Staking Feature is not provided in account output when claiming rewards.19
- denotes that fail to claim staking reward.20
- denotes that fail to claim delegation reward.21
- denotes that the burning of native tokens was not allowed in the transaction capabilities.22
- denotes that the burning of mana was not allowed in the transaction capabilities.23
- denotes that the destruction of accounts was not allowed in the transaction capabilities.24
- denotes that the destruction of anchors was not allowed in the transaction capabilities.25
- denotes that the destruction of foundries was not allowed in the transaction capabilities.26
- denotes that the destruction of nfts was not allowed in the transaction capabilities.255
- denotes that the semantic validation failed.
The identifier of the transaction. Hex-encoded with 0x prefix.
Possible values: [pending
, accepted
, confirmed
, finalized
, failed
]
If 'pending', the transaction is not included yet. If 'accepted', the transaction is included. If 'confirmed' means transaction is included and its included block is confirmed. If 'finalized' means transaction is included, its included block is finalized and cannot be reverted anymore. If 'failed' means transaction is issued but failed due to the transaction failure reason.
Possible values: [1
, 2
, 3
, 4
, 5
, 6
, 7
, 8
, 9
, 10
, 11
, 12
, 13
, 14
, 15
, 16
, 17
, 18
, 19
, 20
, 21
, 22
, 23
, 24
, 25
, 26
, 255
]
Values:
{
"transactionId": "string",
"transactionState": "pending",
"transactionFailureReason": 1
}
{
"transactionId": "0x72f0dfa9ad116ade8bdac8ef291ed2fb8065c6c75d5d3666e8b2053696c94a9e00001000",
"transactionState": "confirmed"
}
Unsuccessful operation: indicates that the provided data is invalid.
- application/json
- Schema
- Example (from schema)
Schema
error objectrequired
The application error code.
The error reason.
{
"error": {
"code": 400,
"message": "invalid data provided"
}
}
Unsuccessful operation: indicates that the endpoint is not available for public use.
- application/json
- Schema
- Example (from schema)
Schema
error objectrequired
The application error code.
The error reason.
{
"error": {
"code": 403,
"message": "not available for public use"
}
}
Unsuccessful operation: indicates that the requested data was not found.
- application/json
- Schema
- Example (from schema)
Schema
error objectrequired
The application error code.
The error reason.
{
"error": {
"code": 404,
"message": "could not find data"
}
}
Unsuccessful operation: indicates that an unexpected, internal server error happened which prevented the node from fulfilling the request.
- application/json
- Schema
- Example (from schema)
Schema
error objectrequired
The application error code.
The error reason.
{
"error": {
"code": 500,
"message": "internal server error"
}
}
Unsuccessful operation: indicates that the node is not synced.
- application/json
- Schema
- Example (from schema)
Schema
error objectrequired
The application error code.
The error reason.
{
"error": {
"code": 503,
"message": "service unavailable"
}
}