User's data

Related endpoints (authenticated user)

These routes return additional user-scoped data. All require Authorization: Bearer <access_token>.

GET and POST /v1.2/users/me

GET /v1.2/users/me

Aggregator endpoint. It proxies the authenticated user sub-routes and returns a compact response: section payloads are directly exposed at top-level keys.

Proxied sections (7):

• GET /v1.2/users/me/address
• GET /v1.2/users/me/balances
• GET /v1.2/users/me/ibans
• GET /v1.2/users/me/signers
• GET /v1.2/users/me/transactions
• GET /v1.2/users/kyc/status
• GET /v1.2/users/me/addressbook

Not included in the aggregator (call separately for performance):

• GET /v1.2/users/me/lending — DeFi lending positions
• GET /v1.2/users/me/pools — DeFi positions across AAVE, Morpho, Hyperliquid
• GET /v1.2/safes/vaults — DeFi vault/pool catalog

When one or more sections fail, an optional errors object is added:

• errors.<section> = { status, message }
• Failed sections are omitted from top-level section keys

Example (aggregated 200):

{
  "addresses": { "count": 3, "wallets": [ { "safeAddress": "0xE0d2...", "chainIds": [100, 421614] } ] },
  "balances": { "type": "crypto", "identifier": "0xE0d2...", "balance": { "tokens": [] } },
  "ibans": { "count": 5, "ibans": [ { "iban": "FR7616748000017481348099624", "status": "active" } ] },
  "signers": { "count": 2, "signers": [ { "id": "AVZs0...", "type": "PASSKEY" }, { "id": "e8d3...", "type": "EOA" } ] },
  "transactions": { "type": "crypto", "total": 3, "data": [] },
  "kycStatus": { "externalUserId": "604a81ce-7246-41e2-a5fd-92cd1cc29943", "kycLevel": "5", "verified": true },
  "addressbook": { "success": true, "data": [ { "id": "b98af44d-...", "name": "H2R Treasury", "crypto": [], "ibans": [] } ] }
}

Example (partial failure):

{
  "addresses": { "count": 3, "wallets": [] },
  "balances": { "type": "crypto", "identifier": "0xE0d2..." },
  "errors": {
    "transactions": { "status": 500, "message": "Internal server error" }
  }
}

POST /v1.2/users/me

Stores arbitrary flat key/value data for the authenticated user. Identity is taken from the JWT — any user identifier in the body is ignored.

Request body:

{
  "data": {
    "email": "jane.doe@example.com",
    "firstName": "Jane",
    "language": "en",
    "optin.newsletter": true,
    "private.apiKey": "sk_live_xxx"
  }
}

Response: { "success": true }

curl -X GET "https://passkeys-testnet.ibex.fi/v1.2/users/me" \
  -H "Authorization: Bearer <token>"

{}

curl -X POST "https://passkeys-testnet.ibex.fi/v1.2/users/me" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "data": {}
  }'

{
  "success": true
}