Limits and billing
Trial restrictions, per-plan sending allowances, time windows, and cancellation behavior.
Trial limits#
Trials are restricted by account and connected-number history. Creating another account does not make an already-used phone number eligible for another trial.
| Allowance | Trial |
|---|---|
| Duration | Three days from email verification. |
| Sessions | One connected session. |
| Total sends | 50 text messages across the whole trial. |
| Daily sends | 20 per UTC calendar day. |
| Sending pace | Three sends per rolling 60 seconds. |
| Recipients | Connected number or support-approved test recipients. |
| Media | Not included. |
Paid plan allowances#
Paid session, monthly, daily, and per-minute allowances are shown on Pricing and before checkout. The purchased price and limits are saved with the subscription; editing a catalog plan does not silently increase an existing customer’s allowance.
Allowances apply across every session and API key in the workspace. UTC calendar boundaries determine daily and monthly resets. The sending pace uses a rolling 60-second window.
What consumes allowance#
A new message reserves allowance before entering the queue. Queued, sending, sent, delivered, read, and uncertain messages count. A replay of the same idempotent request does not create a second reservation.
Messages rejected before gateway dispatch do not count against sending allowance. A successful API response is not evidence that the recipient received a message. New sends pause at the applicable limit; no automatic overage charge is added.
API request rate#
Authenticated public API requests are limited to 120 requests per API key per 60-second rate-limit window, independently of message allowances. Creating more keys does not increase the account’s message quota.
QR retrieval is additionally limited to ten requests per session per minute. Starting a session is limited to three requests per session per ten minutes. Use polling intervals and backoff appropriate for the state you are observing; rate-limit responses do not currently include a Retry-After header.
Payment and cancellation#
Prices are USD before applicable taxes. Payments are processed by Polar under the TurbineWeb billing identity. Cancel subscription renewal in Plans & billing; paid access continues through the current period.
After access expires, new sends and active session operations are restricted, and the worker stops the connection. Stop and delete operations remain available. Existing message metadata can still be read with a valid, authorized read token. Removing a session does not cancel a subscription or issue a refund.