Retry Partner Account Allowances

Retries delegated-trading allowance recovery for a partner-created server-wallet sub-account. The retry takes a short wallet lock, re-checks live chain state, and submits only targets still missing. A submitted target means this retry request submitted a sponsored transaction or user operation.

POST /profiles/partner-accounts/{profileId}/allowances/retry

Retry partner account allowances

cURL

curl --request POST \
  --url https://api.limitless.exchange/profiles/partner-accounts/{profileId}/allowances/retry \
  --header 'Content-Type: application/json' \
  --header 'lmts-api-key: <api-key>' \
  --data '{}'

200

{
  "profileId": 4543,
  "partnerProfileId": 4430,
  "chainId": 84532,
  "walletAddress": "0x1a665817f063Ee15C6C2c05D4315982145825C3D",
  "ready": false,
  "summary": {
    "total": 10,
    "confirmed": 2,
    "missing": 0,
    "submitted": 8,
    "failed": 0
  },
  "targets": [
    {
      "type": "USDC_ALLOWANCE",
      "tokenAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "spenderOrOperator": "0x54d696A602343063000B25a51734E3BbE0Ec80a2",
      "label": "ctf-exchange",
      "requiredFor": "BUY",
      "confirmed": false,
      "status": "submitted",
      "retryable": true,
      "transactionId": "tx_abc123",
      "txHash": "0xabc123...",
      "userOperationHash": "0xdef456...",
      "errorCode": "RPC_READ_FAILED",
      "errorMessage": "<string>"
    }
  ]
}

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

Parameter	Type	Required	Description
profileId	number	Yes	Partner sub-account profile id for the server-wallet child account.

Request body

No request body is required.

{}

Response

Returns the same shape as Check Partner Account Allowances.

{
  "profileId": 4543,
  "partnerProfileId": 4430,
  "chainId": 84532,
  "walletAddress": "0x1a665817f063Ee15C6C2c05D4315982145825C3D",
  "ready": false,
  "summary": {
    "total": 10,
    "confirmed": 2,
    "missing": 0,
    "submitted": 8,
    "failed": 0
  },
  "targets": [
    {
      "type": "USDC_ALLOWANCE",
      "tokenAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "spenderOrOperator": "0x54d696A602343063000B25a51734E3BbE0Ec80a2",
      "label": "ctf-exchange",
      "requiredFor": "BUY",
      "confirmed": false,
      "status": "submitted",
      "transactionId": "tx_...",
      "userOperationHash": "0x...",
      "retryable": false
    }
  ]
}

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

Status	Meaning	Partner action
429	Retry is rate limited. Response includes retryAfterSeconds.	Wait retryAfterSeconds, then call GET again.
409	Another retry is already running for this wallet.	Wait briefly, then call GET again.

429 example

{
  "message": "Allowance retry rate limited",
  "retryAfterSeconds": 30
}

409 example

{
  "message": "Allowance retry already running"
}

Recommended flow

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

curl -X POST "https://api.limitless.exchange/profiles/partner-accounts/4543/allowances/retry" \
  -H "content-type: application/json" \
  -H "lmts-api-key: <tokenId>" \
  -H "lmts-signature: <base64_hmac_sha256_signature>" \
  -H "lmts-timestamp: <iso_8601_timestamp>" \
  -d '{}'

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.

Body

application/json

The body is of type object.

Response

200

application/json

Allowance state after retry submission attempts

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

Show child attributes

targets · object[] · required

Show child attributes