Skip to main content
POST
Redeem voucher
Required scope: vouchers:redeem Rate limit: 60 requests/minute Idempotency: supported via Idempotency-Key header (24h TTL, scoped per API key). See Idempotency. A redemption deducts from the voucher’s balance. If the new balance reaches zero the voucher status moves to redeemed; otherwise it stays completed with the reduced balance.

Path parameters

Headers

Request body

Response

Errors

  • 400 "Voucher is pending and not redeemable" – voucher status is pending.
  • 400 "Voucher is not redeemable" – voucher status is anything other than pending or completed (e.g. already redeemed, voided, refunded).
  • 400 "Cannot redeem an expired voucher"expiry_date has passed.
  • 400 "Redemption amount exceeds available balance"amount is greater than the voucher’s current balance.
  • 404 – Voucher not found in your tenant (or location).
  • 409 "A duplicate request is already being processed. Please wait a moment and try again." – a request with the same Idempotency-Key is still in flight. Retry shortly.
  • 409 "Idempotency-Key was reused with a different request body. Use a fresh Idempotency-Key for a different operation."Idempotency-Key reused with a different request body within the 24h replay window. See Idempotency.
  • 409 "Voucher balance changed concurrently – please retry" – the voucher balance changed underneath the operation (e.g. concurrent redemption). Retry.

Examples