Skip to main content
GET
Get server-wallet allowance readiness for a partner subaccount
Requires HMAC authentication with the account_creation and delegated_signing scopes. API key auth and Privy auth are not accepted.
Checks delegated-trading allowance readiness for a partner-created server-wallet sub-account. The response is based on live chain reads.
  • Route: GET /profiles/partner-accounts/:profileId/allowances
  • Auth: HMAC api-token auth
  • Scopes: account_creation + delegated_signing
  • profileId: child/server-wallet profile id that belongs to the authenticated partner

Path parameters

Response

Response fields

Target fields

  1. Poll this endpoint.
  2. If ready=true, continue with delegated trading.
  3. If targets are missing or failed and retryable=true, call Retry Partner Account Allowances.
  4. If retry submits targets, poll this endpoint again after a short delay.

Example

Pack vault approval

When Packs are enabled and the treasury vault is configured, allowance targets include type: "USDC_ALLOWANCE", label: "parlay-treasury-vault", and requiredFor: "BUY". Existing wallets may need an explicit retry after the vault is enabled. Before preparing a Pack purchase, require that specific target to have confirmed: true and status: "confirmed". A submitted approval is not confirmation. Retry uses the existing unlimited-approval policy and can repair other missing trading targets too. A buy rejected with PACK_ALLOWANCE_REQUIRED includes tokenAddress, spender, and requiredAllowance. See the Partner Packs allowance preflight for the repair and polling sequence.

Path Parameters

profileId
string
required

Response

200