Fair use policy

Who this applies to

This policy applies to every caller of the Telavox APIs — Telavox customers, third-party developers building integrations on behalf of customers, and wholesale partners using our APIs. For customers sold through a wholesale partner, the wholesale partner framework agreement governs the commercial relationship; this page is the public default that applies in the absence of other terms.

What the APIs are for

The APIs exist to let you operate, integrate, and extend the Telavox tenancy you (or your customer) pay for. Building your own product or workflow against them is in scope. Reselling raw API access, building a competing service on top, or using the APIs to evade Telavox commercial terms is not.

Telephony abuse

These are telecommunications APIs, not just data APIs. We do not tolerate use that enables telephony abuse: robocalling, A2P / grey-route SMS abuse, calling-line identification (CLI) spoofing, automated mass dialing campaigns, or any activity that violates the telecommunications regulations of the jurisdictions involved.

Fair use and enforcement

Send the load your use case actually needs. Prefer event-driven and webhook-based integrations over high-frequency polling. Use bulk endpoints where they exist. Be patient with retries (exponential backoff with jitter). Honour Retry-After. The Best practices page covers the specifics.

We do not publish specific thresholds — limits vary by endpoint, change over time, and depend on platform load. Our standard ladder is notify → throttle → block: direct customers and ISVs are contacted through their respective contact channel. Telavox reserves the right to throttle, suspend, or terminate access to protect the platform, its customers, and the telecommunications networks it depends on. We aim to communicate before we act, but reserve the right to act first when downstream harm is imminent.

Identification

Every integration must send a descriptive User-Agent header that identifies the application and a way to reach the team behind it. Wholesale partners must additionally attribute traffic by downstream tenant where applicable, so per-tenant fairness can be enforced under a single integration. Unidentified traffic may be throttled or blocked without notice.

Data, privacy, and security

Tokens are credentials — keep them out of source control, logs, and URLs. Personal data accessed through the APIs is processed under the relevant data-processing agreements with Telavox or your wholesale partner. Suspected token leakage, breaches, or security issues must be reported to Telavox without undue delay.

Lifecycle and deprecations

Lifecycle events — releases, breaking changes, deprecations, sunsets — are announced on the Announcements page with explicit dates. Staying current is part of fair use; integrations that continue calling sunset endpoints after the announced date may be blocked. Material changes to this policy are announced on the same page.

Questions

If you are unsure whether your integration is within the bounds of fair use, reach out before you ship.

Email: support@telavox.se