List active Yotpo Loyalty redemption options and redeem points for a reward, including delayed-deduction checkout flows
domain: loyaltyapi.yotpo.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call GET /api/v2/redemption_options, optionally scoped to a specific customer, to show which redemption options they currently qualify for.
Call POST /api/v2/redemptions with the customer identifier, redemption_option_id, and points_to_redeem (for variable-amount options) to redeem points and receive a coupon code.
For a redeem-now-complete-order-later flow, pass delay_points_deduction: true so points aren't deducted until the resulting coupon code is used on a Create Order call.
If not delaying deduction, apply the returned coupon code to checkout immediately since points are deducted at redemption time.
Handle 423 (locked) responses by retrying with backoff, since they indicate a concurrent redemption race on the same customer.
Known gotchas
Forgetting delay_points_deduction for a hold-then-checkout flow causes points to be deducted immediately even if the order is later abandoned.
Only one of customer_email, pos_account_id, phone_number, or customer_id should be supplied to identify the customer.
A 423 locked response is a real, documented state for concurrent redemption attempts — a naive integration handling only 200/400/404 will mishandle it.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?