Claim a settled position without paying gas
Enqueues a redeem_positions meta-tx for the submitter to broadcast on the user’s behalf — the user pays no gas. Identify the position by (marketId, outcomeIndex) (the compound key on every Position from GET /api/me/positions); the server re-reads the authoritative position from exchange-service, verifies it is redeemable, builds the on-chain payload itself (binary conditionId+indexSets or neg-risk marketId+questionIndex+amount — client-supplied payloads are deliberately not accepted), and queues the job. Returns { jobId, status }; poll GET /api/me/positions/redeem/{jobId} until the job confirms. The credited payout then appears on the vault balance via the standard PositionRedeemed pipeline. API-key (partner) callers MUST include the owner-signed auth bundle (EIP-712 RedeemAuthorization); Privy-JWT (retail) callers omit it. Failures: 400 not_redeemable / neg_risk_not_ready / no_quantity / no_condition_id; 403 no_vault; 404 position_not_found. Rate limit: 10/60s per wallet. Requires vault:write scope and deposit tier ≥ 1.
Body
Market identifier of the position to redeem — the marketId field from the Position payload (GET /api/me/positions).
"PM-WC26-R16-USA-WC26-1910V2"
Outcome index of the held position (0 = YES, 1 = NO). For binary markets this scopes the CTF indexSets bitmask to the single side the user holds; for neg-risk it only disambiguates which Position row to read (the adapter burns both sides in one call regardless).
0 <= x <= 2550
Owner-signed EIP-712 RedeemAuthorization bundle. REQUIRED only for API-key (partner) callers — it binds the redeem to the wallet owner so a spoofable X-User-Wallet header cannot force a third-party redeem. Privy-JWT (retail) callers omit it. Signed struct: RedeemAuthorization{owner, marketId, outcomeIndex, deadline} under domain {name:'PredictStreetRedeem', version:'1', chainId}.
Response
Job accepted (idempotent on payload hash — an identical in-flight redeem returns the existing job).