Send Custom Transaction

Endpoint allows you to send a custom transaction on the specified blockchain. Use this endpoint to initiate transactions with custom parameters.

Overview

Endpoint

• Method: POST

• URL: /wallet/{address}/{chain}/transaction

Parameters

• address: (Path Parameter): Sender's wallet address (string).

• chain: (Path Parameter): Blockchain (string). Available values: polygon.

Request Body

• Media Type: application/json

• Example Value:

{
  "to": "0xf6797c479c7b18de2ea7493291d5f21fede8ff29",
  "data": "0xa30cd29c0000...",  // Hex-encoded transaction data
  "value": 1.5  // Transaction value in cryptocurrency
}

Responses

Success (Code 200)

{
  "transactionHash": "0xe2e830fcc13af572c0cbe970e69c2ebd873cc85b9984099a072709f1ee62305b"
}

• Media Type: application/json

• Example Value: An object containing the transaction hash for the successful custom transaction.

Unauthorized (Code 401)

{
  "code": 401,
  "message": "Please Authenticate"
}

• Media Type: application/json

• Example Value: An error response indicating unauthorized access.

Forbidden (Code 403)

{
  "code": 403,
  "message": "Forbidden"
}

• Media Type: application/json

• Example Value: An error response indicating forbidden access.

Not Found (Code 404)

{
  "code": 404,
  "message": "Wallet Not Found"
}

• Media Type: application/json

• Example Value: An error response indicating that the sender's wallet was not found.

Method Not Allowed (Code 405)

{
  "code": 405,
  "message": "This Method Is Not Supported For Non-Custodial Wallets"
}

• Media Type: application/json

• Example Value: An error response indicating that the method is not allowed for non-custodial wallets.

Internal Server Error (Code 500)

{
  "error": "Internal Server Error"
}

• Media Type: application/json

• Example Value: An error response indicating an internal server error.

Usage

1. Send a POST request to the /wallet/{address}/{chain}/transaction endpoint to initiate a custom transaction.

2. Include the required parameters and request body in the request.

3. Handle the response accordingly based on success, unauthorized access, forbidden access, not found, method not allowed, or internal server error.

Note: Ensure the sender's wallet address and blockchain chain are valid. Verify the user's authentication status and permissions before initiating the custom transaction.