Tokens

Fungible-token routes follow an account-model wallet API against the peer’s configured chaincode (schema family account-model / fungible-token v0.1).

Authenticate with X-Api-Key. Full OpenAPI: API reference.

Contract

Method	Path	Purpose
`POST`	`/api/tokens/issue`	Issue units to a wallet
`POST`	`/api/tokens/transfer`	Transfer between wallets
`GET`	`/api/tokens/redeem/quote`	Quote redemption for an amount
`POST`	`/api/tokens/redeem`	Redeem units from a wallet
`GET`	`/api/tokens/stats`	Network economics / supply snapshot
`GET`	`/api/tokens/{walletId}/balance`	Wallet balance
`GET`	`/api/tokens/{walletId}/history`	Wallet history

These seven routes are the primary public wallet surface. Integrators should treat them as the stable contract; see Upgrade & compatibility.

Wallet operations

Issue

POST /api/tokens/issue
X-Api-Key: <key>
Content-Type: application/json

{
  "walletId": "wallet-a",
  "usdAmount": 10,
  "coinUnits": 100
}

Transfer

{
  "fromWalletId": "wallet-a",
  "toWalletId": "wallet-b",
  "amount": 25
}

Redeem quote

GET /api/tokens/redeem/quote?amount=10
X-Api-Key: <key>

Redeem

{
  "walletId": "wallet-a",
  "amount": 10
}

Routes such as /api/tokens/init, /distribute, /top-up-reserve, /reverse, and audit-export require X-Admin-Api-Key and are operator tooling, not the partner wallet contract. They may appear in OpenAPI for completeness but are not the primary integration path.

Success shape

Successful submits typically return:

{
  "success": true,
  "transactionId": "…"
}

Evaluates (quote, balance, history, stats) return { "success": true, "result": … }. Failures use the error envelope.

Next: Assets

Tokens

Contract

Wallet operations

Admin routes (out of scope)

Success shape