Integration
Task Status
Overview
When a purchase is submitted, Otonum returns a taskId immediately and processes rewards asynchronously.
For exact status routes and response schema, use the API Reference.
Why Asynchronous Processing
Asynchronous handling keeps checkout responsive while Otonum evaluates campaigns, applies business rules, updates balances, and sends notifications.
- Checkout is not blocked by reward computation
- High transaction volume is handled without degrading response times
- Purchase recording remains durable even if reward computation later fails
Standard Pattern
For most integrations, do not poll continuously.
- Submit purchase and receive
taskId - Confirm order in your system
- Let Otonum process in background
- Let Otonum notify the member
When Polling Makes Sense
| Scenario | Why poll |
|---|---|
| In-app reward display | Immediate reward feedback is required in your own UI |
| Reconciliation workflows | Backend jobs need explicit completion checks |
| Debugging | Expected reward did not appear |
Task Status Values
| Status | Meaning | Action |
|---|---|---|
processing | Queued or in progress | Wait and check later |
completed | Rewards applied to member balance | Display confirmation if needed |
failed | Processing failed | Investigate with support |
Handling Failed Tasks
Do not resubmit the same activity with the same reference.
Contact support with the taskId for investigation.
Last modified on