Platform REST API — Tokens

Deploy ERC-20 tokens and read their metadata.

See Platform REST API for authentication.

Deploy

POST /api/token/deploy

Deploys an ERC-20 and sends the supply to an address you nominate. User-level auth — this spends gas.

Input	Type	Notes
user_id, user_pwd	string	Required
tokenName	string	Required
tokenSymbol	string	Required
tokenDescription	string	Optional
totalSupply	number	Required
decimals	number	Optional. Default 18, range 0–18
buyingFee	number	Optional. Basis points — 100 = 1%
sellingFee	number	Optional. Basis points
feeAddress	string	Optional. Where fees accrue
mintable	boolean	Optional
destinationAddress	string	Receives the supply

{
  "success": true,
  "data": {
    "contractAddress": "0x…",
    "transactionHash": "0x…",
    "transferHash": "0x…"
  }
}

transactionHash is the deployment; transferHash is the supply transfer to destinationAddress.

Transfer fees affect AMM pairs

A token with a buying or selling fee takes a cut on every transfer, including transfers into and out of an AMM pair. Fee-on-transfer tokens need the router's fee-supporting swap methods, and a naive getAmountsOut will over-estimate the output. Set fees to zero unless you specifically want this.

Decimals are fixed at deployment

decimals cannot be changed afterwards. Use 18 unless you have a reason not to — it is what every tool and pair on this chain assumes by default.

Read

GET /api/token/info/:address?user_id=

Name, symbol, decimals and supply. User-level auth.

POST /api/token/info_by_address

The same, by request body.

GET /api/token/list

GET /api/token/tokens

Tokens deployed through the platform.

For tokens not deployed here, read them from the chain data API or call decimals(), symbol() and name() directly.