Skip to main content
POST
Claim a winning Pack position
Requires HMAC with trading and delegated_signing. Put the managed owner in body field onBehalfOf; do not send x-on-behalf-of. Use the winning purchase’s position UUID. For a WON position, the backend handles sponsored conditional-token approval and factory redemption. Repeat the identical position/account request to progress through APPROVAL_PENDING, CLAIM_PENDING, and CLAIMED. The payout goes to the managed wallet. txHash belongs to the current step. Only a CLAIMED response establishes it as the confirmed redemption transaction. transactionId and userOperationHash identify sponsored submission and are not interchangeable with a mined transaction hash. Back off on 429 and wallet-busy conflicts before resuming the same claim. Inspect PACK_TRANSACTION_REVERTED, fix its cause, and resume the same position. On PACK_SUBMISSION_UNKNOWN, stop blind retries and reconcile the transaction; use Confirm Claim once you have its mined redemption receipt. The position’s status remains WON after claiming. Verify the claim response’s CLAIMED status or the position’s claimTxHash. See the SDK claim helpers for bounded convergence. This route shares the partner-owner limit of 10 requests per 10 seconds.

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.

Headers

lmts-timestamp
string
required

ISO-8601 HMAC signing timestamp.

lmts-signature
string
required

Base64 HMAC-SHA256 signature. Sign the method, path including query, and exact body with the timestamp.

Path Parameters

id
string<uuid>
required

Body

application/json
onBehalfOf
integer
required

Owned managed server-wallet profile ID.

Required range: 1 <= x <= 2147483647
Example:

12345

Response

Successful response

parlayId
string<uuid>
required
status
enum<string>
required
Available options:
APPROVAL_PENDING,
CLAIM_PENDING,
CLAIMED
txHash
string

Transaction hash for the current step. When CLAIMED, the confirmed redemption transaction.

transactionId
string
userOperationHash
string

Sponsored user operation identifier, not a mined transaction hash.