API Reference
SupportStatusSign UpLogin

Send EGLD from account to account

post
https://api.tatum.io/v3/egld/transaction

/v3/egld/transaction

2 credits per API call.


Send EGLD from account to account.

This operation needs the private key of the blockchain address. Every time the funds are transferred, the transaction must be signed with the corresponding private key. No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey or signatureId. PrivateKey should be used only for quick development on devnet versions of blockchain when there is no risk of losing funds. In production, Tatum KMS should be used for the highest security standards, and signatureId should be present in the request. Alternatively, using the Tatum client library for supported languages.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
length between 62 and 62

Account address of the sender

string
required
length between 62 and 62

Account address of the receiver or smart contract

string
required

Value to be sent.

fee
object

Custom defined fee. If not present, it will be calculated automatically.

string

Additional data that can be passed to a blockchain transaction as a data property; must be in the hexadecimal format

string
required
length between 64 and 64

Private key of sender address. Private key, or signature Id must be present.

Responses

Updated 9 days ago

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 9 days ago