Allways Access / Developersv1Get your API key
Endpoints

GET/v1/account

Which account your key belongs to, your credit balance, and where to top it up.

Request

GET /v1/account. Needs x-api-key. No parameters.

Requestcurl
curl "$API/v1/account" -H "x-api-key: $KEY"

Response

FieldMeaning
accountIdWhich account this key belongs to; quote it in support requests
displayNameThe account's name, as the app shows it
apiKeyCreatedAtWhen the key sent with this request was minted, unix seconds; null if unknown
balanceCredits available; fractional, since a top-up buys TAO ÷ taoPerCredit
pendingCredits held by pending exchanges
depositAddressTop-up address, or null
reservationCostCredits per exchange
creditAssetAsset accepted for credits
taoPerCreditTAO that buys one credit right now; null while the price is unknown
minTopUpTaoSmallest deposit that is credited, in TAO
Responsejson
{
  "accountId": "9f1c2e4a-7b3d-4c58-9e21-0a1b2c3d4e5f",
  "displayName": "swift-otter-4821",
  "apiKeyCreatedAt": 1756900000,
  "balance": 3,
  "pending": 1,
  "depositAddress": "5HGjWAeFDfFCWPsjFQdVV2Msvz2XtMktvgocEZcCj68kUMaw",
  "reservationCost": 1,
  "creditAsset": "alpha token",
  "taoPerCredit": "0.0066",
  "minTopUpTao": "0.03"
}

Errors

HTTPCodeExtra fieldsWhen
401unauthorized—Missing or invalid x-api-key
403geo_blocked—Request from a blocked region
429rate_limitedretryAfterOver the limit; see Rate limits

Notes

  • Call this first when a key is handed to you: displayName and accountId say whose account you are spending from, and several keys on several accounts are easy to mix up.
  • Regenerating a key invalidates the old one, so a key that still authenticates is the current one and apiKeyCreatedAt says when it was minted. A 401 means the key was replaced or revoked.
  • To top up, send TAO to depositAddress; one credit costs taoPerCredit, and deposits under minTopUpTao are not credited. No API write is needed. See Credits.
  • Each exchange costs reservationCost credits.