ClickSend · Rate Limits

Clicksend Rate Limits

The ClickSend v3 API applies per-account request throttling to protect the platform. Callers should send messages in batches (the send endpoints accept a collection of messages in a single request) rather than issuing one HTTP request per recipient. Effective throughput is also governed by account credit balance, sender/number provisioning, and destination carrier limits rather than a single published requests-per-second figure. Specific numeric limits are not published as fixed values and are not reconciled in this artifact.

Clicksend Rate Limits is the machine-readable rate-limit profile for ClickSend on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and messages.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Communications, SMS, MMS, Voice, and Email.

3 Limits Throttle: 429
CommunicationsSMSMMSVoiceEmailPostMessagingRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Per-account request throttling; batch recipients into a single send call rather than one request per message.
Batch Size per Send request
messages
see provider documentation
The send endpoints accept a messages[] collection; large batches are the intended path for bulk delivery.
Carrier / Destination Throughput destination
messages
carrier-dependent
Downstream SMS/MMS/voice throughput is subject to destination carrier and number-type limits.

Policies

Batching
Send multiple recipients per request via the messages[] array to reduce request count.
Backoff Strategy
On HTTP 429, implement exponential backoff with jitter and retry.
Prepaid Balance
Sending stops when account credit is exhausted; monitor balance via GET /account.

Sources