Jump to
Ctrl
+
/

Prepare A Fungible Token Transfer From Address

POST
/blockchain-tools/{blockchain}/{network}/transactions/prepare-token-from-address

Using this endpoint customers can prepare a fungible token transfer from an address with private and public keys. The address doesn’t have to belong to a wallet. The response will include the transaction fee in Wei.

Path Parameters

blockchain string Required

Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.

network string Required

Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "mordor" are test networks.

Query Parameters

context string Optional

In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

Request Body Schema application/json

context string Optional

In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

data object Required
item object Required
amount string Required

Representation of the amount to be transferred

contract string Required

Represents the contract address of the token, which controls its logic. It is not the address that holds the tokens.

nonce string Optional

Represents the sequential running number for an address, starting from 0 for the first transaction. E.g., if the nonce of a transaction is 10, it would be the 11th transaction sent from the sender's address.

recipient string Required

The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient.

sender string Required

Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sender.

fee object Required
exactAmount string Required

Representation of the exact amount to be transfered.

priority string Required

Represents the fee priority of the automation, whether it is "slow", "standard" or "fast"

transactionType string Optional

Representation of the transaction type. For Ethereum-Classic and Binance Smart Chain there is no need to provide "transactionType" in the request.

Response Schema

apiVersion string Required

Specifies the version of the API that incorporates this endpoint.

2023-04-25
requestId string Required

Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.

601c1710034ed6d407996b30
context string Optional

In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

yourExampleString
data object Required
item object Required
amount string Required

Representation of the amount to be transferred

1.09340
nonce string Optional

Represents the sequential running number for an address, starting from 0 for the first transaction. E.g., if the nonce of a transaction is 10, it would be the 11th transaction sent from the sender's address.

0
recipient string Required

The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient.

0x534bd102153ef199abae8296a2fae4599fc44cdc
sender string Required

Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sender.

0x0902a667d6a3f287835e0a4593cae4167384abc6
blockchainSpecific object Required
dataHex string Optional

Representation of the data in hex value

0x0079006f00750072004100640064006900740069006f006e0061006c00440061007400610048006500720065
sigHash string Required

Representation of the hash that should be signed

9f59f25bc9f6cbff293ceee32c1fb25ae82fab23a99b860e26cad800ceadd123
fee object Required

Defines the amount of the transaction fee.

gasLimit string Required

Represents the amount of gas used by this specific transaction alone.

552020
gasPrice string Required

Represents the price offered to the miner to purchase this amount of gas.

2500000007
maxFeePerGas string Required

Representation of the max fee per gas value

2000000008
maxPriorityFeePerGas string Required

Representation of the max priority fee per gas value

2000000000
transactionType string Required

Representation of the transaction type

access-list-transaction

Credits Cost : 1000 Credits for 1 Results

Was this page helpful?
Yes
No
Powered by
Language
URL

{
    "apiVersion": "2023-04-25",
    "requestId": "601c1710034ed6d407996b30",
    "context": "yourExampleString",
    "data": {
        "item": {
            "amount": "1.09340",
            "nonce": "0",
            "recipient": "0x534bd102153ef199abae8296a2fae4599fc44cdc",
            "sender": "0x0902a667d6a3f287835e0a4593cae4167384abc6",
            "blockchainSpecific": {
                "dataHex": "0x0079006f00750072004100640064006900740069006f006e0061006c00440061007400610048006500720065",
                "sigHash": "9f59f25bc9f6cbff293ceee32c1fb25ae82fab23a99b860e26cad800ceadd123",
                "fee": {
                    "gasLimit": "552020",
                    "gasPrice": "2500000007",
                    "maxFeePerGas": "2000000008",
                    "maxPriorityFeePerGas": "2000000000"
                },
                "transactionType": "access-list-transaction"
            }
        }
    }
}