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 to create a message signing transaction
The information about a transaction that signs a message. You can provide the message either as raw data or as structured data.
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"
- Org-Controlled/User-Controlled
- Web3
The information about the destination EVM_EIP_191_Signature
. Refer to Transaction sources and destinations for a detailed introduction about the supported sources and destinations for each transaction type.
- EVM_EIP_191_Signature
- EVM_EIP_712_Signature
- BTC_BIP_137_Signature
- BTC_BIP_322_Signature
- COSMOS_ADR_36_Signature
The description of the message signing transaction.
"Transaction to sign a message initiated from a wallet"
The custom category for you to identify your transactions.
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"