Skip to main content
POST
Cancel Transfer

Authorizations

X-API-Key
string
header
default:sk_your_secret_key_here
required

Your partner secret key (server-side only)

Headers

X-Request-Id
string<uuid>

UUID for request tracing. Para returns one if omitted.

Idempotency-Key
string
required

Save a new key for this manual recovery intent and reuse it with the same body for HTTP retries.

Required string length: 1 - 256

Path Parameters

walletId
string<uuid>
required

Wallet UUID. A malformed or inaccessible wallet ID returns 404.

Example:

"0a1b2c3d-4e5f-6789-abcd-ef0123456789"

transactionId
string<uuid>
required

Original persisted /transfer transaction ID.

Body

application/json
maxExecutionFeeWei
string
required

Positive uint256 execution-gas fee ceiling for this replacement in native-token base units. Bounds gasLimit times gasPrice (type 0) or maxFeePerGas (type 2), excluding separate chain fees such as L1 data fees. Para selects and saves the replacement fees once, within this ceiling.

Pattern: ^[0-9]{1,78}$
Example:

"1000000000000000"

Response

Manual recovery accepted or replayed; poll the original transaction for its outcome.

transactionId
string<uuid>
required
Example:

"550e8400-e29b-41d4-a716-446655440000"

walletId
string<uuid>
required
walletType
enum<string>
required
Available options:
EVM,
SOLANA
intentKind
enum<string>
required

REST operation that created the record.

Available options:
transfer,
sign_transaction,
yield
status
enum<string>
required

pending and submitted are nonterminal. confirmed and reverted are verified chain outcomes. failed can report a signing or broadcast error, or a verified same-nonce winner; historical broadcast and monitoring-timeout errors can retain an uncertain chain outcome. Treat unknown future values as nonterminal. For sponsored operations, inclusion is submitted with stage included until receipt verification. Successful execution with verified token delivery is confirmed; an included execution revert is reverted. Unknown submission stays nonterminal, and unresolved token evidence remains pending with stage delivery_unverified. Legacy EVM transfer and sign_transaction broadcasts remain submitted during durable reconciliation after the 30-minute active window. Receipt resolution requires canonical block identity, at least two confirmations, and finalized-block evidence. Timeout, RPC errors, and nonce consumption without an identified winner are unresolved, not payment failure. Solana broadcasts require finalized signature status and also retain unresolved monitoring context. A verified Para automatic-retry or manual speed-up variant resolves the same payment as confirmed or reverted. A verified cancellation or unrelated identified same-nonce winner leaves the original failed with REPLACED or CANCELLED; inspect monitoring for the actual winner's outcome. Historical failed / monitor_timeout records remain uncertain until chain-backed reconciliation corrects them. Historical failed/broadcast records can also be eligible for manual recovery when the original is verified as still pending.

Available options:
pending,
submitted,
confirmed,
reverted,
failed
createdAt
string<date-time>
required
manualRecovery
object
required

Present in manual-recovery POST/replay and single-transaction GET responses. Not included in transaction-list summaries. State tracks recovery processing; use the parent status and monitoring to establish the payment or cancellation outcome.

executionMode
enum<string>

Sponsored records use sponsored; legacy responses may omit this field.

Available options:
legacy,
sponsored
chainId
string

EVM chain ID (EVM records only).

network
enum<string>

Solana network (Solana records only).

Available options:
SOLANA,
SOLANA_DEVNET
to
string

Destination address. Absent for Solana sign_transaction records because Para does not decode arbitrary Solana instructions.

value
string

Transfer amount in smallest unit (wei / lamports / token smallest unit), or EVM sign_transaction value when supplied.

tokenAddress
string

Token contract (ERC-20 / SPL mint) address if a token transfer, else absent. Always absent for sign_transaction records.

monitoring
object

Optional durable monitoring metadata for legacy EVM and Solana broadcasts. Active monitoring hands off after 30 minutes without changing unresolved chain outcome to failed. After 24 hours, escalation retains unresolved state. Healthy pending checks stay at most five minutes apart during the first 24 hours, then may back off to one hour. RPC errors and missing context use backoff capped at one hour. After observing receipt or signature evidence, checks for finality, confirmations, or canonical chain evidence run every 60 seconds regardless of age. Unsupported finality evidence or missing legacy context remains unresolved and requires operational follow-up.

hash
string | null

Original transaction hash. Null or absent before signing; an identified same-nonce winner is exposed separately in monitoring.winningHash. Sponsored operations expose this after inclusion; never a UserOperation hash.

blockNumber
string

Block number as a decimal string (present when confirmed or reverted).

blockHash
string
failureStage
enum<string>

Stage at which the pipeline failed. monitor_timeout appears only on historical records and does not establish chain failure.

Available options:
mpc_sign,
signature_apply,
signer_verify,
broadcast,
monitor_timeout
failureCode
string

Structured broadcast error code, or REPLACED / CANCELLED when a verified same-nonce winner superseded the original transaction.

failureMessage
string

Truncated error message (max 512 chars).

submittedAt
string<date-time>

Set when status first moves to submitted.

resolvedAt
string<date-time>

Set when status reaches a terminal value (confirmed, reverted, failed).