Textmagic · Rate Limits

Textmagic Rate Limits

The Textmagic REST API (v2) applies per-account request throttling to protect platform stability. Specific per-endpoint request-per-second or request-per- minute ceilings are not published in the public documentation, so the values here are placeholders pending reconciliation. Bulk and high-volume sends are expected to be performed through bulk sessions rather than rapid single-message loops. Outbound message throughput is additionally governed by carrier and sender-type (10DLC, toll-free, alphanumeric) deliverability rules.

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

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

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

Tagged areas include SMS, Text Messaging, Messaging, Communications, and CPaaS.

3 Limits Throttle: 429
SMSText MessagingMessagingCommunicationsCPaaSRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Per-account request throttling on the REST API; exact ceiling not published.
Outbound Message Throughput account
messages
see provider documentation
Governed by sender type and carrier rules (10DLC, toll-free, alphanumeric).
Bulk Sessions account
jobs
separate from single-message sends
Large sends should use bulk sessions rather than rapid single-message loops.

Policies

Use Bulk Sessions
Submit large campaigns via bulk send to avoid per-request throttling on single-message endpoints.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.

Sources