Skip to main content
POST
Confirm a Pack claim
Requires HMAC with trading and delegated_signing. Put the managed owner in body field onBehalfOf; do not send x-on-behalf-of. Use this recovery endpoint when a claim submission response was lost or reported PACK_SUBMISSION_UNKNOWN, and you have found the mined redemption transaction. The backend verifies its successful receipt and factory redemption event against the expected recipient and compound token. Pass the factory redemption transaction hash in txHash. A buy hash, approval hash, or user operation hash cannot confirm the claim. Successful confirmation returns status: "CLAIMED". The position’s settlement status remains WON, with claimTxHash recorded. 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

txHash
string
required

Mined factory redemption transaction hash; not an approval, buy, or user operation hash.

Pattern: ^0x[0-9a-fA-F]{64}$

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.