Skip to main content
GET
Check partner account allowances
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

Authorizations

lmts-api-key
string
header
required

Scoped API token with HMAC-SHA256 signing. Requires three headers: lmts-api-key (token ID), lmts-timestamp (ISO-8601), lmts-signature (Base64-encoded HMAC). See Authentication docs for details.

Path Parameters

profileId
integer
required

Partner sub-account profile ID for the server-wallet child account.

Response

Live allowance state for the server-wallet child profile

profileId
integer
required

Child/server-wallet profile ID being checked

Example:

4543

partnerProfileId
integer
required

Authenticated parent partner profile ID

Example:

4430

chainId
integer
required

Chain where allowance targets were checked

Example:

84532

walletAddress
string
required

Managed server-wallet address for the child profile

Example:

"0x1a665817f063Ee15C6C2c05D4315982145825C3D"

ready
boolean
required

True when every target is confirmed on chain

Example:

false

summary
object
required
targets
object[]
required