Skip to main content

Wallets — Reference

partner-wallets routes use Authorization: Bearer $PARTNER_TOKEN (Dashboard/JWT).

GET /v1/partner-wallets — list​

PUT /v1/partner-wallets — upsert (idempotent)​

curl -X PUT "$BASE_URL/v1/partner-wallets" \
  -H "Authorization: Bearer $PARTNER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "network": "base",
    "walletRole": "PARTNER_MARGIN",
    "address": "0x4444444444444444444444444444444444444444"
  }'

GET /v1/wallets/validate — preflight​

UNRESOLVED — auth claim pending

Documented as public, but currently JWT-gated in the running service. Call with $PARTNER_TOKEN until resolved.

curl "$BASE_URL/v1/wallets/validate?address=0x4444…4444&network=base" \
  -H "Authorization: Bearer $PARTNER_TOKEN"
# → { "valid": true, "format": "EVM" }