Accounts API

Resolve who the caller is before READ, DECIDE, or EXECUTE. Business identity uses your API key; wallet identity uses the end-user smart wallet JWT. These routes do not move funds — they return profile metadata linked to the credential.

At a Glance

Canonical	Legacy alias	Auth	Use when
GET /accounts/business	/business/me	sk_live_…	Verify merchant key, display business name, check status
GET /accounts/wallet	/wallet/me	Smart wallet JWT	Resolve EVM + Solana addresses for EXECUTE; confirm session

Alias responses include X-Torque-Canonical-Path. Full route map: API Layout.

GET /api/v1/accounts/business

Returns the Business record associated with the Bearer API key (same key as Checkout and Platform READ).

business-me.sh

export TORQUE_KEY="sk_live_…"

curl -sS "https://app.torque.fi/api/v1/accounts/business" \
  -H "Authorization: Bearer $TORQUE_KEY" \
  | jq '.'

Response (200)

{
  "id": "…",
  "name": "Acme Corp",
  "status": "active",
  "logo": "https://…",
  "currency": "USD",
  "timezone": "America/New_York"
}

Errors: 401 invalid key · 403 business inactive.

GET /api/v1/accounts/wallet

Returns the user linked to the smart wallet JWT. Use before POST /execute/** to confirm which addresses the server will force as sender.

wallet-me.sh

export WALLET_JWT="<smart_wallet_jwt>"

curl -sS "https://app.torque.fi/api/v1/accounts/wallet" \
  -H "Authorization: Bearer $WALLET_JWT" \
  | jq '.'

Response (200)

{
  "subject": "user_…",
  "email": "user@example.com",
  "evmWalletAddress": "0x…",
  "solanaWalletAddress": "…"
}

Errors: 401 invalid or expired JWT. There is no partner API to mint wallet JWTs — see Authentication.

At a Glance

GET /api/v1/accounts/business

Response (200)

GET /api/v1/accounts/wallet

Response (200)

See Also