Sign Transfer Coin/Native

API Documentation: Sign Transfer Coin/Native

Overview

This API endpoint allows you to Sign and Broadcast an Ethereum transaction to transfer coin / native token.

• HTTP Method: POST
• Endpoint: /api/v1/wallet/eth/send/coin

Request Body Parameters

• subId (required): this will be used to determine which key used to sign. The type is string.
• chainId (required): the network's chain ID.
• to (required): the destination EVM address that will receive the coin.
• amount (required): in the wei format.

Example Request Body

{      
    "subId": "...",    
    "chainId" : 17000,
    "to" : "0xeF236f1b35B2105836540c23d055d1BFb6c5db52",
    "amount": 3000000
}

Request

Request Headers

• X-CLIENT-ID: (required): Client ID which was generated when register in Xellar TSS API Service Dashboard.
• X-SIGNATURE: (required): Calculated signature, please refer to Authorization section.
• X-TIMESTAMP: (required): Request timestamp in RFC3339 format.

Example Request Syntax

curl -X POST -H "Content-Type: application/json" -H "x-client-id: $YOUR_CLIENT_ID" -H "x-client-secret: $YOUR_CLIENT_SECRET" -d '{
    "subId": "...",    
    "chainId" : 17000,
    "to" : "0xeF236f1b35B2105836540c23d055d1BFb6c5db52",
    "amount": 3000000
}' <BASE_URL>/api/v1/wallet/eth/send/coin

Response

The response will include a JSON object with the following properties:

• status (number): The HTTP status code of the response (e.g., 200 for success).
• message (string): A message providing additional information about the operation.
• data (object): An object containing the request information.
• data.requestId (string): The unique identifier for the request.

Example Response

{
    "status": 200,
    "message": "Sign transfer coin is in progress",
    "data": {
        "requestId": "9c276eb2-e0e1-4789-bd54-42d5e920379f"        
    }
}