Transactions
For the most up-to-date information, refer to the API Reference.
🚧 The information provided in this section cannot be programmatically updated and may be subject to inconsistencies over time.
- Testnet:
http://platform.canary.enjin.io/graphql
- Mainnet:
http://platform.enjin.io/graphql
This is an overview of some of the most commonly used operations in the Enjin Platform Schema.
AcknowledgeEvents​
The AcknowledgeEvents
mutation allows you to confirm the processing of specific events by acknowledging them and removing them from the cache. This helps maintain cache integrity and ensures efficient system operation by eliminating unnecessary data.
- GraphQL
- Response
mutation AcknowledgeEvents{
AcknowledgeEvents(
uuids: ["25f506ef-92a1-40a9-b034-60f9ab5045da"]
)
}
{
"data": {
"AcknowledgeEvents": true
}
}
UpdateTransaction​
The UpdateTransaction
mutation enables you to update an existing transaction with new information. This is useful for maintaining accurate transaction records and tracking the lifecycle of transactions.
- GraphQL
- Response
mutation UpdateTransaction{
UpdateTransaction(
id: 7
signedAtBlock: 320100
)
}
{
"data": {
"UpdateTransaction": true
}
}
RetryTransactions​
The RetryTransactions
mutation provides a mechanism to retry transactions that have previously failed. This is particularly useful for addressing transaction failures caused by temporary issues such as network congestion or gas price spikes.
- GraphQL
- Response
mutation RetryTransactions{
RetryTransactions(ids: [175])
}
{
"data": {
"RetryTransactions": true
}
}