Data semantics
A detection is created from a device notification. Its source is always android_notification or provider_api, and verified_by_bank is always false — Wolet has no access to bank ledgers. utr is null when the notification doesn't contain one. Show these states honestly in your UI.
Error codes
| HTTP | code | Meaning |
|---|---|---|
invalid_request | 400 | A parameter is missing or malformed |
unauthorized | 401 | Missing or invalid API key |
plan_required | 403 | Your plan doesn't include API access |
not_found | 404 | The resource doesn't exist |
already_decided | 409 | Event already confirmed or rejected |
duplicate_suspected | 422 | Confirming would duplicate another confirmed event |
rate_limited | 429 | Too many requests — retry after the Retry-After header |
internal_error | 500 | Something went wrong on our side |
Rate limits
600 requests per minute per live key, 120 per sandbox key.
Sandbox vs live
| Sandbox | Live | |
|---|---|---|
Key prefix | wlt_test_ | wlt_live_ |
Data | Generated demo events | Your merchants' detections |
Webhooks | Delivered | Delivered |
Billing | Free | Business plan |
Versioning
Breaking changes ship as a new version (/v2). Additive fields can appear at any time — ignore unknown fields.