#Users

End-users and their Static Wallet Address — one permanent address per user, reused for every payment

3 endpoints. Generated from docs/openapi.yaml v1.0.0.

#GET/v1/users

List your users · Auth: bearer API key · operationId: listUsers

Your users, newest first (by creation time). Scoped to your tenant — nobody else's users are ever visible.

total is counted through the SAME filter as the rows, so it is the size of the filtered set, not of your whole user base: page with offset until you have total rows. The page is ordered on figures the database cannot compute (a USD total needs the price feed), so at most 2000 matching users are read; total counts no further than that, and truncated: true says the cap was hit — narrow the filter.

balance_usd, balances[].usd and card_balance are price-feed estimates for display, with no _base twin; read exact balances from GET /v1/users/{externalId}/balances.

Reserved internal accounts (the card-programme float pot) are excluded, so this list agrees with the user counts your dashboard shows.

from/to accept either a bare IST calendar day (YYYY-MM-DD, the whole day INCLUDED on both ends) or a full RFC 3339 instant with an offset. Anything else is a 400 rather than a silently ignored filter.

#Parameters

#Responses

200 response body

{
  "users": [
    {
      "user_id": "user-42",
      "account_kind": "end_user",
      "created_at": "2026-08-31T09:15:00.000Z",
      "balance_usd": "125.40",
      "balances": [
        {
          "asset_id": "usdt_trc20",
          "symbol": "USDT",
          "amount": "1.5",
          "usd": null
        }
      ],
      "card_balance": "string",
      "last_active_at": "2026-08-31T09:15:00.000Z"
    }
  ],
  "total": 1,
  "truncated": true,
  "limit": 1,
  "offset": 1
}

#Example request

curl -X GET 'https://api.cryptoinfra.build/v1/users?from=2026-08-01&to=2026-08-31' \
  -H 'Authorization: Bearer ck_live_your_key'

#POST/v1/users

Create a user and derive its address · Auth: bearer API key · operationId: createUser

Creates a user under your tenant and derives their Static Wallet Address — one permanent TRON address. Every asset in GET /v1/assets lands on that one address; addresses is a list so a client reads it the same way whatever it holds. Idempotent on external_user_id: replaying returns the existing user and address (still 201).

#Request body

application/json · required

#Responses

201 response body — UserAddresses

{
  "user_id": "string",
  "addresses": [
    {
      "chain": "tron",
      "address": "string"
    }
  ]
}

#Example request

curl -X POST 'https://api.cryptoinfra.build/v1/users' \
  -H 'Authorization: Bearer ck_live_your_key' \
  -H 'Content-Type: application/json' \
  -d '{
  "external_user_id": "10482"
}'

#GET/v1/users/{externalId}/addresses

Read a user's Static Wallet Address · Auth: bearer API key · operationId: getUserAddresses

#Parameters

#Responses

200 response body — UserAddresses

{
  "user_id": "string",
  "addresses": [
    {
      "chain": "tron",
      "address": "string"
    }
  ]
}

#Example request

curl -X GET 'https://api.cryptoinfra.build/v1/users/string/addresses' \
  -H 'Authorization: Bearer ck_live_your_key'