Check Partner Account Allowances
Checks delegated-trading allowance readiness for a partner-created server-wallet sub-account. Requires HMAC authentication with account_creation and delegated_signing scopes. Status is based on live chain reads.
account_creation and delegated_signing scopes. API key auth and Privy auth are not accepted.- 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
Recommended flow
- Poll this endpoint.
- If
ready=true, continue with delegated trading. - If targets are
missingorfailedandretryable=true, call Retry Partner Account Allowances. - If retry submits targets, poll this endpoint again after a short delay.
Example
Authorizations
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
Partner sub-account profile ID for the server-wallet child account.
Response
Live allowance state for the server-wallet child profile
Child/server-wallet profile ID being checked
4543
Authenticated parent partner profile ID
4430
Chain where allowance targets were checked
84532
Managed server-wallet address for the child profile
"0x1a665817f063Ee15C6C2c05D4315982145825C3D"
True when every target is confirmed on chain
false