Drop transaction
This operation cancels or drops a pending transaction.
The behavior depends on the current transaction status:
submitted,pending_screening,pending_authorization,pending_signature: the transaction is cancelled directly (no fee required).broadcasting: the transaction is replaced via RBF (Replace-By-Fee). You must supply thefeefield in the request body.
Provide cobo_transaction_id in the request body to identify the transaction by its provider-assigned ID instead of the local UUID in the path.
success or failed status. RBF drop is not supported on VET, TRON, TVET, SOL, TON chains or gasless (paymaster) transactions.Headers
Path Parameters
The UUID of the wallet that owns the transaction. Retrieve this value from the id field returned when the wallet was created.
The UUID of the user transaction to drop, returned as id by the transfer or contract-call endpoints.
Body
Request payload for cancelling a transaction.
fee is required for Broadcasting (RBF drop); omit for pre-broadcast cancel.
A client-supplied identifier for the replacement transaction.
255Custom fee parameters for the replacement transaction. Required when the transaction is broadcasting (RBF drop).
- EIP1559FeeRequest
- EVMLegacyFeeRequest
- SOLFeeRequest
The provider-side transaction ID to cancel. The transaction ID can be retrieved from the transfer or contract call response.
255Response
Successful Response
Shared response payload for drop/speedup/resend operations.
Pagination metadata for list responses.
Supports both legacy offset-based and cursor-based pagination.
Cursor fields (has_more, after, before) are populated for
cursor-paginated endpoints. Legacy fields (offset, limit) are
populated when the caller uses the deprecated offset parameter.