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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-01.
Written by API Evangelist on 2026-07-01 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/clicksend-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.