TorqueTorque

Search docs

Search Torque documentation pages & sections

Integrator Wallets

Give each user in your app a Torque wallet: deposit addresses, unified balance, and withdraw via Connect. Manage keys and setup in the developer portal.

Quick start

#StepAction
1API keyPortal → Overview → Create key. Server only.
2ProvisionPOST /accounts/end-users with externalUserId + email
3DepositsReturn addresses. Poll GET …/deposits or optional webhook in Settings
4WithdrawSettings → your app URL (https://yourapp.com). Add callback on your server
5TestEnable Portal test withdraw in Settings before your app ships

Provision

Call on signup. externalUserId is your stable user id; email is their account email (required in v1 for Connect). Idempotent on externalUserId.

provision.sh
curl -sS -X POST "https://app.torque.fi/api/v1/accounts/end-users" \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "externalUserId": "player_48291",
    "email": "user@example.com"
  }'

Response includes addresses, portfolioSummary, and capabilities. See Accounts API.

Deposits

Return addresses in your deposit UI. Encode each address in a client-side QR (same pattern as Torque Transfer → Request) — QR value is the raw address string from addresses.evm, addresses.solana, or addresses.btcDeposit. No server QR endpoint.

Poll GET /accounts/end-users/{id}/deposits or set an optional deposit webhook in portal Settings (end_user.deposit.detected). Preview QR in the developer portal wallet row.

Withdraw setup

Portal → Settings → Withdraw setup → enter your app URL (e.g. https://yourapp.com). Torque registers callback https://yourapp.com/torque/connect/callback. Add that route on your backend — users return with ?code=… after approving withdraw.

Portal test withdraw — try before your app is live. Callback: https://developers.torque.fi/connect/callback.

WhoAction
YouSave app URL in developer portal Settings
Your serverPOST /connect/authorize/session (redirect_uri, PKCE, optional externalUserId)
UserApproves on Torque /connect/oauth
Your serverCallback receives ?code=… → POST /connect/token
Your serverPOST /execute/transfers/… with delegated JWT

Connect details: Actions — third-party handoff, Authentication.

See also

Was this helpful?