Wallet APIs

Token Balances

This endpoint allows you to retrieve balance tied to a particular address on a specific chain.The response of this API will let you understand in details about all your assets.

Request
Security:
path Parameters
chain
required
string

Chain name (example: bsc, ethereum, matic...)

Enum: "ethereum" "bsc" "matic" "celo" "avalanche" "xinfin" "zilliqa" "solana" "fantom" "bsc-testnet" "matic-testnet" "rinkeby-testnet"
Example: bsc
address
required
string
Default: "demo.eth"

Any valid address or ENS

Example: demo.eth
Responses
200
401
get/v1/{chain}/address/{address}/assets
Request samples
curl -i -X GET \
  'https://api.unmarshal.com/v1/:chain/address/:address/assets?auth_key=YOUR_API_KEY_HERE'
Response samples
application/json
[
  • {},
  • {
    },
  • {
    }
]

Transaction History V1

The token transactions API fetches the list of all transactions in wallet address

Our Bank statements often let us understand the financial positions of a bank account. Similarly for a Crypto wallet , the transactions gives the wallet holder a detailed analysis of the inbound and out bound transfers thereby keeping the wallet apprised of all the happenings in their wallet.

Unmarshal Transaction APIs are smart enough to differentiate the kind of operation a particular transaction was made for. It will let a user understand if the transaction was was for a send or receive or the amount was staked or un-staked , or if the transactions was for adding or removing liquidity .

Request
Security:
path Parameters
chain
required
string

Chain name (example: bsc, ethereum, matic...)

Enum: "ethereum" "bsc" "matic" "celo" "avalanche" "xinfin" "zilliqa" "solana" "fantom" "bsc-testnet" "matic-testnet" "rinkeby-testnet"
Example: bsc
address
required
string
Default: "demo.eth"

Any valid address or ENS

Example: demo.eth
query Parameters
page
number >= 1
Default: 1

Page you want to query

pageSize
number
Default: 25

Number of records to be fetched per page

Example: pageSize=5
contract
string

Valid contract address

Responses
200
401
get/v1/{chain}/address/{address}/transactions
Request samples
curl -i -X GET \
  'https://api.unmarshal.com/v1/:chain/address/:address/transactions?page=1&pageSize=5&contract=string&auth_key=YOUR_API_KEY_HERE'
Response samples
application/json
{
  • "page": 1,
  • "total_pages": 178,
  • "items_on_page": 1,
  • "total_txs": 355,
  • "transactions": [
    ]
}

Transaction History V2

The token transactions API fetches the list of all transactions in wallet address

Our Bank statements often let us understand the financial positions of a bank account. Similarly for a Crypto wallet, the transactions gives the wallet holder a detailed analysis of the inbound and out bound transfers thereby keeping the wallet apprised of all the happenings in their wallet.

Unmarshal Transaction APIs are smart enough to differentiate the kind of operation a particular transaction was made for. It will let a user understand if the transaction was was for a send or receive or the amount was staked or un-staked , or if the transactions was for adding or removing liquidity .

Request
Security:
path Parameters
chain
required
string

Chain name (example: bsc, ethereum, matic...)

Enum: "ethereum" "bsc" "matic" "celo" "avalanche" "xinfin" "zilliqa" "solana" "fantom" "bsc-testnet" "matic-testnet" "rinkeby-testnet"
Example: bsc
address
required
string
Default: "demo.eth"

Any valid address or ENS

Example: 0xfc43f5f9dd45258b3aff31bdbe6561d97e8b71de
query Parameters
page
number >= 1
Default: 1

Page you want to query

pageSize
number
Default: 25

Number of records to be fetched per page

Example: pageSize=5
contract
string

Valid contract address

Responses
200
401
get/v2/{chain}/address/{address}/transactions
Request samples
curl -i -X GET \
  'https://api.unmarshal.com/v2/:chain/address/:address/transactions?page=1&pageSize=5&contract=string&auth_key=YOUR_API_KEY_HERE'
Response samples
application/json
{
  • "page": 1,
  • "total_pages": 410,
  • "items_on_page": 2,
  • "total_txs": 818,
  • "transactions": [
    ]
}

Transaction Details

The transaction detail API is one such End Point which gives as much details possible for a specific transaction on a specific given chain.

All we need is the transaction hash and the entire history of the transaction is presented to anyone looking for all minor details pertaining to the particular transaction

Request
Security:
path Parameters
chain
required
string

Chain name (example: bsc, ethereum, matic...)

Enum: "ethereum" "bsc" "matic" "celo" "avalanche" "xinfin" "zilliqa" "solana" "fantom" "bsc-testnet" "matic-testnet" "rinkeby-testnet"
Example: bsc
transactionHash
required
string
Default: "0x8e1337b81ff3c1a7e3796c74c9dc084566b6e043cd69968e9b1d2336cd3d8e64"

Any valid transaction hash

Responses
200
401
get/v1/{chain}/transactions/{transactionHash}
Request samples
curl -i -X GET \
  'https://api.unmarshal.com/v1/:chain/transactions/:transactionHash?auth_key=YOUR_API_KEY_HERE'
Response samples
application/json
{
  • "id": "string",
  • "from": "string",
  • "to": "string",
  • "fee": "string",
  • "date": 0,
  • "status": "string",
  • "type": "string",
  • "block": 0,
  • "value": "string",
  • "nonce": 0,
  • "description": "string",
  • "sent": [],
  • "received": [],
  • "others": []
}

Profit and Loss

Request
Security:
path Parameters
address
required
string
Default: "demo.eth"

Any valid address or ENS

Example: demo.eth
query Parameters
contract
required
string

Valid contract address

Request Body schema: application/json
object
Responses
200
401
get/v2/ethereum/address/{address}/userData
Request samples
application/json
{ }
Response samples
application/json
{
  • "quote_rate": 1.88,
  • "total_fees_paid": 0.00408196,
  • "total_fees_paid_usd": 12.35876252184,
  • "average_token_price": 0.6777538233562116,
  • "overall_profit_loss": 1390.998826376863,
  • "current_holding_quantity": 1157,
  • "percentage_change_24H": 3.87773,
  • "price_change_24H": 81.37875199999999
}