post
https://api.fiscanner.net/Vouchers/Redeem
Redemption Workflow:
The redemption process follows these steps:
- Validate the voucher exists and is active
- Check redemption eligibility (not already redeemed, not expired)
- Mark voucher as "booking" to prevent concurrent redemption
- Publish redemption event for downstream processing
- Return acceptance confirmation
Concurrency Control:
The system implements optimistic concurrency control by immediately updating the voucher
status to "booking" upon redemption request. This prevents double-spending scenarios
in high-concurrency environments.
Event-Driven Processing:
The actual redemption processing occurs asynchronously through domain events. This allows
for complex business logic, external service integration, and proper error handling
without blocking the API response.
Validation Rules:
- Voucher must exist in the system
- Voucher cannot be already redeemed
- Voucher must not be expired or voided
- Operator must have appropriate permissions
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
200OK
202Redemption request accepted and processing initiated.
400Invalid request data or voucher already redeemed.
401Authentication token is missing, invalid, or expired.
404Specified voucher does not exist in the system.