Device quotas, API usage and billing rules
Request refund
Balance and top-ups → Request refund → My refund applications
Select one of your credited recharge orders to request a refund.
Applications cover unspent recharge credit only. Submission does not hold your balance; available funds are checked during review.
Device quotas count devices used; API quotas count successful server requests. They are separate measures; device count cannot determine API usage.
Which operations count toward API usage?
| Actions | Counted? |
|---|---|
| Successful activation, validation, heartbeat or release | Each success counts once; separate heartbeats on the same day each count. |
| Failed requests, e.g. invalid key or insufficient allowance | Not counted |
| Retry with the same Idempotency-Key and return the original result | Not counted again |
| Local CheckFeature or signed-cache check | Not counted; no server request |
| Query or issue licenses with a management API Key | Not included in this runtime API quota |
Do repeated requests count a device more than once?
Device quota counts current activations and is returned on release. Ordinary licenses remain counted while offline; floating licenses also return quota when their leases expire.
Device overage uses the highest occupancy in the quota month. Switching devices within that capacity is not charged again. History and incurred charges are retained.
For example, 100 devices running 8 hours a day, 22 days a month, with 10-minute heartbeats produce this many heartbeats alone: 105,600 calls. Add 100 activations and one extra validation per device each day, giving 107,900 calls.
Extra validations are assumed for this example; actual usage depends on your app. In Online usage estimator adjust devices, run time and request interval.
How is plan overage charged?
For a plan with 100,000 API calls and 0.0001 USD per extra call: 120,000 successful calls mean 20,000 extra, with an API overage fee of 2 USD.
Plans allowing overage deduct balance at administrator prices. The cumulative amount is rounded to cents and only its increase is charged, so tiny per-call prices do not cause repeated rounding charges.
Device overage is separate: excess devices × device unit price. A hard limit rejects further requests for that quota. Insufficient balance also rejects the next chargeable request. Rejected requests do not add usage.
Unlimited API quotas have no API overage fee. A quota of zero includes no free calls, so overage rules apply from the first successful request. For included quotas, prices and limits, see Current plan, these figures are examples only.
License seat limits and workspace device quotas are separate limits. Both ordinary and floating licenses use workspace quota for current valid activations.
After rotating through 10 devices, release each replaced device first. Keeping at most 3 valid activations uses at most 3 device quota units.
Device history retains previously used devices and does not represent current quota occupancy.
When do package duration and quota start?
Buy 1, 3, 6 or 12 months. Pay the total once; the package starts after successful payment.
API allowances reset each month; unused calls do not roll over.
Purchased packages use quota months anchored to their start date. Valid device registrations remain counted across quota months.
Device quota counts current activations and is returned on release. Ordinary licenses remain counted while offline; floating licenses also return quota when their leases expire.
Each quota month uses the applicable allowance and rates. Adverse changes to published rules require advance notice; paid package fees stay fixed.
Without a purchase, administrator defaults apply by UTC calendar month. Default device fees use monthly invoices; default API overage is deducted from balance immediately. A purchased plan uses its own period's quotas, without adding default quotas.
If quota or balance shortages reject a runtime request, existing offline signatures remain valid under their original rules. Vendors can release devices in the console without consuming the customer's runtime API quota.
Plan email notifications
Administrators choose notification types and reminder days in System settings. The default is 7 days before expiry; you can set 7, 3 and 1 days.
Workspace owners choose email types and language in Plans and billing. All are enabled by default, including purchase and automatic renewal notifications.
Reminders use the final expiry including advance renewals and continuous gifted coverage. Monthly quota resets do not trigger expiry emails.
Email preferences and balance-funded automatic renewal are separate. Opting out of email does not disable an enabled renewal.
Uses the existing verification email service, sender and queue. Customers can also opt out.