Redeem voucher
Vouchers
Redeem voucher
Deduct an amount from a voucher’s balance. Supports idempotency.
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
| Parameter | Type | Notes |
|---|---|---|
code | string | Voucher code, max 50 characters |
Headers
| Header | Required | Notes |
|---|---|---|
Idempotency-Key | no | Up to 256 characters. Cached response replays for 24 hours. |
Request body
| Field | Type | Required | Notes |
|---|---|---|---|
amount | decimal (string) | yes | Greater than 0 |
notes | string | no | Optional internal note |
Response
Errors
400 "Voucher is pending and not redeemable"– voucher status ispending.400 "Voucher is not redeemable"– voucher status is anything other thanpendingorcompleted(e.g. alreadyredeemed,voided,refunded).400 "Cannot redeem an expired voucher"–expiry_datehas passed.400 "Redemption amount exceeds available balance"–amountis greater than the voucher’s currentbalance.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 sameIdempotency-Keyis 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-Keyreused 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.