Sandbox assets and discovery

Once you have an API key, make GET /api/v1/me your first call. It tells you which identity and capabilities your token maps to.

GET https://sandbox-api.nuvante.io/api/v1/me

{
  "data": {
    "user": {
      "id": "apikey:4b2c9e7a-1d3f-4a6b-8c5e-7f9a0b1c2d3e",
      "email": "dev@sandbox.nuvante.test",
      "displayName": "Dev User",
      "role": "member"
    },
    "capabilities": {
      "initiateTransaction": true,
      "cancelOwnTransaction": true,
      "viewDashboard": true,
      "viewParticipants": true,
      "viewReserves": false,
      "viewAuditLog": false,
      "manageApiKeys": false,
      "manageOwnTeam": false,
      "runOwnConformancePack": false,
      "generateReserveProof": false,
      "manageIssuedAssets": false,
      "manageParticipants": false,
      "manageUsers": false,
      "manageAccounts": false,
      "overrideTransaction": false,
      "manageOwnAgents": false
    },
    "participant": {
      "id": "c3d5e7f9-2a4b-4c6d-8e0f-1a3b5c7d9e2f",
      "kind": "clearing_member",
      "name": "Example Bank"
    }
  }
}

A few notes on the response:

• user.id starts with apikey: when you call with an API key. When you call from a signed-in portal session, it's the user's UUID.
• participant.id is your participant UUID. You'll need it for lookups in the admin console.
• participant.kind is either clearing_member or stablecoin_issuer.
• defaultRtgs shows up when your participant has a linked RTGS account.

GET /api/v1/me/balances reads the trustlines on your Stellar account, matches them against the IssuedAsset records we know about, and leaves out any zero balances. It's the only public way to find out which assets you actually hold.

GET https://sandbox-api.nuvante.io/api/v1/me/balances

{
  "data": [
    {
      "amount": "250000.00",
      "assetCode": "GBPC",
      "assetIssuer": "GABCDE...stellar_account_address"
    }
  ],
  "meta": {
    "totalGbp": "250000.00"
  }
}

assetIssuer is the issuer's Stellar account address (a public key string). When you call POST /api/v1/transactions, you need the issuer's Nuvanté participant UUID instead, which is the issuer ID assigned to your participant during onboarding.

To initiate a transaction you need two things: the issuer's participant UUID and the asset code (for example GBPC). Both are assigned during onboarding and confirmed by your Nuvanté integration contact.

API keys never get runOwnConformancePack or manageApiKeys, whatever the participant kind.

• Authentication: the scope list and how to create API keys.
• Wallet permissions per chain: what your wallet needs before a lock.