Skip to main content

Wallets

:::info Dashboard endpoints Wallet configuration uses a dashboard bearer token (Authorization: Bearer $PARTNER_TOKEN), not X-API-Key. Manage these from the partner dashboard, or obtain a token via the OIDC flow described in Authentication. :::

List partner wallets​

curl "$BASE_URL/v1/partner-wallets" -H "Authorization: Bearer $PARTNER_TOKEN"

Upsert partner wallet (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"
  }'

Wallets are keyed (partner, network, role) — re-PUT replaces the prior wallet for that role. Existing in-flight transactions keep the wallet pinned at quote-acceptance time.

base is used above only as an example. network accepts any network enabled for your account, and address must be in the address format of that network.

Validate an address (preflight)​

Public — no credential required. Check an address before you attach it to a wallet or beneficiary.

curl "$BASE_URL/v1/wallets/validate?address=0x4444444444444444444444444444444444444444&network=base"
# → { "valid": true, "format": "evm" }

Next steps​