What wede counts
wede counts the production operations of your tenant against your annual plan. Sandbox operations (wede_test_ keys) are never counted.
Every production event counts once toward the annual event allowance of your plan, when it is created, whatever the channel and whether it is delivered or not.
Communications are counted the way the providers charge them, when they are sent, confirmed or not:
Only what is sent through a provider of wede is taken from the channel allowance of your plan, and what goes above it is charged. What is sent through your organisation’s own providers is counted and never charged. What your organisation receives (for example a reply by SMS from a field team) is counted and never taken from your plan nor charged (see Communications model).
Usage is counted per calendar year.
See your usage
Annual usage
GET /v1/tenant/billing returns a usage object with your counters for the current year:
Usage for a period
GET /v1/tenant/usage?from=<ISO 8601>&to=<ISO 8601> counts the production events created in that period. Both parameters are required (400 invalid_payload otherwise).
offline_events are events that were captured without connectivity and received through Sync. by_channel groups events by channel_used.
Usage alerts
wede checks usage every day and emails your tenant contact as your production events progress through the annual allowance of your plan. An alert is sent when 50, 40, 30, 20 and 10 percent of the allowance remains, and when the allowance is reached (0 percent remaining). Each alert is sent at most once per calendar year. wede also sends alerts as each channel allowance is consumed.Licence notices
The administrators of your organisation get an email 30, 7 and 1 days before your licence ends, when it ends and the 30-day renewal period starts, and when it becomes inactive. Each notice is sent once. The licence is renewed in Billing in the dashboard.Beyond the allowance
wede never suspends your tenant for exceeding its annual event allowance. Operational continuity comes first: your events, sync, webhooks and dispatch keep working exactly as before. Events above the allowance are reported asoverage_events in the usage object of GET /v1/tenant/billing and, from November 2026, charged at your price per event on the monthly invoice. When usage above your plan costs more each month than the next plan, Billing suggests that plan.