Skip to main content
POST
/
v1
/
transactions
/
{operationId}
/
recover
Recover Transaction
curl --request POST \
  --url https://api.example.com/v1/transactions/{operationId}/recover

Documentation Index

Fetch the complete documentation index at: https://docs.rebelfi.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

Endpoint: POST https://api.rebelfi.io/v1/transactions/:operationId/recover
Recover a transaction that was broadcast to the blockchain but not properly submitted to RebelFi. Use this when you broadcast a signed transaction but forgot to call submit-hash, or if the submit-hash call failed.

​
Path Parameters

ParameterTypeRequiredDescription
operationIdnumberYesOperation ID the transaction belongs to

​
Request Body

FieldTypeRequiredDescription
txHashstringYesOn-chain transaction hash that was broadcast
transactionIdnumberNoTarget transaction ID. If omitted, matches the first unsigned transaction.

​
Example Request

curl -X POST "https://api.rebelfi.io/v1/transactions/123/recover" \
  -H "x-api-key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "txHash": "5UfD...xyz"
  }'

​
Example Response

{
  "success": true,
  "transactionId": 456,
  "txHash": "5UfD...xyz"
}

​
Errors

CodeDescription
OPERATION_NOT_FOUNDOperation ID doesn’t exist
TRANSACTION_NOT_FOUNDNo matching transaction found in the operation
INVALID_OPERATION_STATUSOperation is not in a recoverable state
Recovery is useful when your application crashes after broadcasting but before calling submit-hash. The transaction is already on-chain — recovery links it back to the operation so RebelFi can track confirmation.