Tokens
Call the public token gateway for account-model wallet ops (fungible-token v2.0, multi-token). Authenticate with a dashboard-minted X-Api-Key. Do not dial node hosts.
Copy the exact gateway URL from Dashboard → API Keys. Machine-readable contract: API reference → Tokens. NFT configuration is not yet public.
Contract
| Method | Path | Scope |
|---|---|---|
GET | /token-gateway/whoami | Resolve networkId + URLs from the API key alone |
GET | /token-gateway/{networkId}/tokens | token:read |
POST | /token-gateway/{networkId}/tokens | token:create |
POST | /token-gateway/{networkId}/tokens/{tokenId}/issue | token:issue |
POST | /token-gateway/{networkId}/tokens/{tokenId}/transfer | token:transfer |
POST | /token-gateway/{networkId}/tokens/{tokenId}/redeem | token:redeem |
GET | /token-gateway/{networkId}/tokens/{tokenId}/redeem/quote | token:read |
GET | /token-gateway/{networkId}/tokens/{tokenId}/wallets/{walletId}/balance | token:read |
GET | /token-gateway/{networkId}/tokens/{tokenId}/wallets/{walletId}/history | token:read |
GET | /token-gateway/{networkId}/wallets/{walletId}/portfolio | token:read |
Treat these routes as the stable partner wallet contract. See Upgrade & compatibility. Mint keys with token:* scopes in Dashboard → Developer → API Keys.
Create and list tokens
A single network can host many independent coins. The primary / deploy-time token uses tokenId=default. Create additional tokens with token:create:
| Method | Path | Purpose |
|---|---|---|
GET | /token-gateway/{networkId}/tokens | List tokens on the network |
POST | /token-gateway/{networkId}/tokens | Create a token (token:create) |
POST | /token-gateway/{networkId}/tokens/{tokenId}/issue | Issue for a specific token |
POST | /token-gateway/{networkId}/tokens/{tokenId}/transfer | Transfer for a specific token |
GET | /token-gateway/{networkId}/tokens/{tokenId}/wallets/{walletId}/balance | Balance for a specific token |
GET | /token-gateway/{networkId}/wallets/{walletId}/portfolio | Holdings across all tokens |
Wallet operations
Replace {networkId} and {tokenId} from your key card (whoami or Dashboard → API Keys). Examples use the public gateway path.
Issue
POST /token-gateway/{networkId}/tokens/{tokenId}/issue
X-Api-Key: <key>
Content-Type: application/json
{
"walletId": "wallet-a",
"usdAmount": 10,
"coinUnits": 100
}
Transfer
POST /token-gateway/{networkId}/tokens/{tokenId}/transfer
X-Api-Key: <key>
Content-Type: application/json
{
"fromWalletId": "wallet-a",
"toWalletId": "wallet-b",
"amount": 25
}
Redeem quote
GET /token-gateway/{networkId}/tokens/{tokenId}/redeem/quote?amount=10
X-Api-Key: <key>
Redeem
POST /token-gateway/{networkId}/tokens/{tokenId}/redeem
X-Api-Key: <key>
Content-Type: application/json
{
"walletId": "wallet-a",
"amount": 10
}
Admin routes (out of scope)
Operator-only token tooling (init, distribute, top-up-reserve, reverse, audit-export) is not part of the public partner contract. It is omitted from the published OpenAPI. Use the gateway routes above for integration.
Success shape
Successful submits typically return:
{
"success": true,
"transactionId": "…"
}
Evaluates (quote, balance, history) return { "success": true, "result": … }. Failures use the error envelope.