Skip to main content
POST
/
transactions
/
{transaction_id}
/
drop
import cobo_waas2
from cobo_waas2.models.create_transfer_transaction201_response import (
    CreateTransferTransaction201Response,
)
from cobo_waas2.models.transaction_rbf import TransactionRbf
from cobo_waas2.rest import ApiException
from pprint import pprint

# See configuration.py for a list of all supported configurations.
configuration = cobo_waas2.Configuration(
    # Replace `<YOUR_PRIVATE_KEY>` with your private key
    api_private_key="<YOUR_PRIVATE_KEY>",
    # Select the development environment. To use the production environment, change the URL to https://api.cobo.com/v2.
    host="https://api.dev.cobo.com/v2",
)
# Enter a context with an instance of the API client
with cobo_waas2.ApiClient(configuration) as api_client:
    # Create an instance of the API class
    api_instance = cobo_waas2.TransactionsApi(api_client)
    transaction_id = "f47ac10b-58cc-4372-a567-0e02b2c3d479"
    transaction_rbf = cobo_waas2.TransactionRbf(
        request_id="f47ac10b-58cc-4372-a567-0e02b2c3d479",
        fee=cobo_waas2.TransactionRequestFee(
            cobo_waas2.TransactionRequestFixedFee(
                fee_type="EVM_EIP_1559", token_id="TRON"
            )
        ),
    )

    try:
        # Drop transaction
        api_response = api_instance.drop_transaction_by_id(
            transaction_id, transaction_rbf=transaction_rbf
        )
        print("The response of TransactionsApi->drop_transaction_by_id:\n")
        pprint(api_response)
    except Exception as e:
        print(
            "Exception when calling TransactionsApi->drop_transaction_by_id: %s\n" % e
        )


{
  "request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "transaction_id": "c986cb3b-1301-412f-9450-13a52c43a95f",
  "status": "Submitted"
}
import cobo_waas2
from cobo_waas2.models.create_transfer_transaction201_response import (
    CreateTransferTransaction201Response,
)
from cobo_waas2.models.transaction_rbf import TransactionRbf
from cobo_waas2.rest import ApiException
from pprint import pprint

# See configuration.py for a list of all supported configurations.
configuration = cobo_waas2.Configuration(
    # Replace `<YOUR_PRIVATE_KEY>` with your private key
    api_private_key="<YOUR_PRIVATE_KEY>",
    # Select the development environment. To use the production environment, change the URL to https://api.cobo.com/v2.
    host="https://api.dev.cobo.com/v2",
)
# Enter a context with an instance of the API client
with cobo_waas2.ApiClient(configuration) as api_client:
    # Create an instance of the API class
    api_instance = cobo_waas2.TransactionsApi(api_client)
    transaction_id = "f47ac10b-58cc-4372-a567-0e02b2c3d479"
    transaction_rbf = cobo_waas2.TransactionRbf(
        request_id="f47ac10b-58cc-4372-a567-0e02b2c3d479",
        fee=cobo_waas2.TransactionRequestFee(
            cobo_waas2.TransactionRequestFixedFee(
                fee_type="EVM_EIP_1559", token_id="TRON"
            )
        ),
    )

    try:
        # Drop transaction
        api_response = api_instance.drop_transaction_by_id(
            transaction_id, transaction_rbf=transaction_rbf
        )
        print("The response of TransactionsApi->drop_transaction_by_id:\n")
        pprint(api_response)
    except Exception as e:
        print(
            "Exception when calling TransactionsApi->drop_transaction_by_id: %s\n" % e
        )

Authorizations

​
BIZ-API-KEY
string
header
required

The API key. For more details, refer to API key.

In the API playground, enter your API secret, and your API key will be accordingly calculated.

Path Parameters

​
transaction_id
string<uuid>
required

The transaction ID.

Body

application/json

The request body to drop or to speed up transactions

The information about the request to drop or to speed up transactions.

​
request_id
string
required

The request ID that is used to track a transaction request. The request ID is provided by you and must be unique within your organization.

Example:

"f47ac10b-58cc-4372-a567-0e02b2c3d479"

​
fee
Fixed · object
required

The preset properties to limit transaction fee.

In the fixed fee model, the transaction fee is a fixed amount within a certain amount of period regardless of the transaction size or network congestion, which can vary between different chains. For more information about the fixed fee model, refer to Fee models.

You can specify the maximum fee amount to limit the transaction fee. The transaction will fail if the transaction fee exceeds the specified maximum fee amount.

Switch between the tabs to display the properties for different transaction fee models.

​
source
Org-Controlled/User-Controlled · object

The information about the transaction source types Org-Controlled and User-Controlled. Refer to Transaction sources and destinations for a detailed introduction about the supported sources and destinations for each transaction type.

  • For UTXO-based chains: both address and included_utxos are optional. If both address and included_utxos are provided, the UTXOs must belong to the specified address. If neither address nor included_utxos is provided, the system will select UTXOs from the wallet associated with wallet_id.
  • For account-based chains: You need to provide address otherwise the token transfer will fail. However, when estimating fees for a transfer, address is not required.

For detailed rules on address and included_utxos in both regular and RBF transactions, see Address and included_utxos usage.

Switch between the tabs to display the properties for different transaction sources.

​
category_names
string[]

The custom category for you to identify your transactions.

​
description
string

The description of the RBF transaction.

Example:

"Speedup transaction"

​
auto_fuel
enum<string>

The mode of transaction fee payment using Fee Station. Currently, Fee Station supports transactions made with MPC Wallets on EVM-compatible chains, TRON, and Solana. For more details, refer to Fee Station.

  • ProActiveAutoFuel: Always use Fee Station to pay transaction fees.
  • PassiveAutoFuel: Use Fee Station only when the source address balance is insufficient to cover transaction fees.
  • UsePortalPreference: Use fueling strategy based on the Portal configuration.
  • DisableAutoFuel: Do not use Fee Station for transaction fee payment under any circumstances.

If this parameter is not specified, it defaults to the behavior of UsePortalPreference.

Note: TRON and Solana does not support PassiveAutoFuel due to its fee delegation mechanism.

Available options:
PassiveAutoFuel,
ProActiveAutoFuel,
UsePortalPreference,
DisableAutoFuel
Example:

"PassiveAutoFuel"

Response

The request was successful.

​
request_id
string
required

The request ID that is used to track a transaction request. The request ID is provided by you and must be unique within your organization.

Example:

"f47ac10b-58cc-4372-a567-0e02b2c3d479"

​
transaction_id
string
required

The transaction ID.

Example:

"c986cb3b-1301-412f-9450-13a52c43a95f"

​
status
enum<string>
required

The transaction status. For more details including sub-statuses, please refer to Transaction statuses and sub-statuses.

Available options:
Submitted,
PendingScreening,
PendingAuthorization,
PendingSignature,
Broadcasting,
Confirming,
Completed,
Failed,
Rejected,
Pending
Example:

"Submitted"