Skip to main content
POST
Retry missing server-wallet approvals for a partner subaccount
Requires HMAC authentication with the account_creation and delegated_signing scopes. API key auth and Privy auth are not accepted.
Retries delegated-trading allowance recovery for a partner-created server-wallet sub-account. The retry operation:
  • takes a short lock for the wallet
  • re-checks live chain state before submitting
  • submits only targets that are still missing
  • returns submitted only for targets this request submitted as a sponsored transaction or user operation
  • Route: POST /profiles/partner-accounts/:profileId/allowances/retry
  • Auth: HMAC api-token auth
  • Scopes: account_creation + delegated_signing
  • profileId: child/server-wallet profile id that belongs to the authenticated partner

Path parameters

Request body

No request body is required.

Response

Returns the same shape as Check Partner Account Allowances.
submitted does not mean the target is already confirmed on-chain. It means this retry request submitted a sponsored transaction or user operation. Poll the GET endpoint again after a short delay.

Error responses

429 example

409 example

  1. Poll Check Partner Account Allowances.
  2. If ready=true, continue.
  3. If targets are missing or failed and retryable=true, call this endpoint.
  4. If this endpoint returns submitted targets, poll GET again after a short delay.
  5. If 429, wait retryAfterSeconds.
  6. If 409, wait briefly and call GET again.

Example

Path Parameters

profileId
string
required

Response

200 - undefined