Liquidation Bots
Confirm Bot Transaction
Refresh the cached state of a bot after one of its transactions is mined
POST
Tells the API that a transaction affecting the bot has been mined, so it drops its cached reads of the bot and its activity. The next Get Liquidation Bot or List Bot Transactions goes to the chain. Use it after the steps of Connect Bot to Market, Bot Owner Action and Fund Bot.
Nothing is recorded. The bot’s state is read from the chain every time, so there is nothing a confirmation could store. Skipping it only means waiting out the caches: 15 seconds for state, 20 seconds between activity reads.
The only checks are that the transaction was mined and did not revert. The API does not check which contract it targeted, what it called or who sent it, so a successful confirmation says nothing about the bot. Unlike other confirmations, an unreadable receipt answers
409 TX_NOT_FOUND, not 404.
Path Parameters
string
required
Bot ID.
Body Parameters
string
required
Hash of the mined transaction.
Response Fields
object
