Integration FAQ
General
Does Otonum notify members automatically?
Yes. Notification behavior depends on tenant configuration.
Should I poll task status after every purchase?
Usually no. Most integrations submit purchases and let processing complete in background.
Can one API key be used across applications?
No. Each Api Key is associated with an application.
Members and Enrollment
What if a member loses their personal code?
Use member lookup flows documented in the API Reference.
Can a member be enrolled in multiple partner programs?
Yes. Wallets remain isolated by tenant.
What if enrollment returns already exists?
Treat duplicate enrollment responses as expected state and continue with retrieval flows.
Purchases and Rewards
Can the same purchase be submitted twice?
Use unique reference values. Duplicate submissions are treated as idempotency outcomes.
What if no campaign matches a purchase?
Purchase recording still succeeds. No reward is granted for that event.
Can multiple campaigns reward one purchase?
Yes, if multiple campaign conditions match.
Vouchers
Are voucher operations fully available in sandbox?
Some voucher operations are restricted in sandbox. Validate expected behavior during test planning.
Can vouchers be used across tenants?
No. Voucher scope is tenant-specific.
Technical
Where is the API key sent?
In the x-api-secret header.
What about rate limiting?
Implement backoff and retry policies for throttling responses.