Authorizations
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.
Body
The request body for making a contract call.
The information about a transaction that interacts with a smart contract
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.
"f47ac10b-58cc-4372-a567-0e02b2c3d479"
The chain ID, which is the unique identifier of a blockchain. You can retrieve the IDs of all the chains you can use by calling List enabled chains.
"ETH"
The information about the transaction source type. Refer to Transaction sources and destinations for a detailed introduction about the supported sources and destinations for each transaction type.
Switch between the tabs to display the properties for different transaction sources.
- Org-Controlled/User-Controlled
- Safe{Wallet}
- Web3
The information about the transaction destination. Refer to Transaction sources and destinations for a detailed introduction about the supported sources and destinations for each transaction type.
- EVM_Contract
- SOL_Contract
- STELLAR_Contract
The description of the contract call transaction.
"Transaction to call a smart contract initiated from a wallet"
The custom category for you to identify your transactions.
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.
- Fixed
- EVM_EIP_1559
- EVM_Legacy
- UTXO
- SOL
- FIL
Transaction processing type. Possible values are:
AutoProcess
(default): After the transaction is constructed, it will be automatically signed and broadcast.BuildOnly
: Set to this value if you want to build the transaction first without automatically signing and broadcasting it. You can manually call the Sign and broadcast transaction operation to complete the signing and broadcasting process.
AutoProcess
, BuildOnly
"AutoProcess"
The mode of transaction fee payment using Fee Station. Currently, Fee Station supports EVM-compatible and TRON transactions initiated from MPC Wallets (Organization-Controlled) and Custodial Wallets (Web3 Wallets). 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 the transaction fees.UsePortalPreference
: Use payment preferences set on Cobo Portal.
Please note that the TRON chain does not support PassiveAutoFuel
due to its fee delegation mechanism.
PassiveAutoFuel
, ProActiveAutoFuel
, UsePortalPreference
"PassiveAutoFuel"
Response
The request was successful.
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.
"f47ac10b-58cc-4372-a567-0e02b2c3d479"
The transaction ID.
"c986cb3b-1301-412f-9450-13a52c43a95f"
The transaction status. For more details including sub-statuses, please refer to Transaction statuses and sub-statuses.
Submitted
, PendingScreening
, PendingAuthorization
, PendingSignature
, Broadcasting
, Confirming
, Completed
, Failed
, Rejected
, Pending
"Submitted"