46elks · Rate Limits

46Elks Rate Limits

46elks does not publish fixed public request-per-second quotas for its HTTP API. In practice throughput is governed by carrier and operator constraints on SMS and voice delivery, by your prepaid account balance, and by anti-abuse controls. High volume senders are onboarded and rate-shaped with 46elks support. Specific numeric limits are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring messages, concurrent_calls, requests, and balance.

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

Tagged areas include CPaaS, SMS, MMS, Voice, and Rate Limiting.

4 Limits Throttle: 429
CPaaSSMSMMSVoiceRate LimitingQuotasThrottling

Limits

SMS Send Rate account
messages
see provider support
Effective throughput is shaped by operator/carrier limits and account standing.
Voice Call Concurrency account
concurrent_calls
see provider support
Governed by allocated call channels; extra channels can be rented per month.
API Requests account
requests
see provider support
No fixed public RPS documented; abusive traffic is throttled.
Account Balance account
balance
prepaid
Sending stops when the prepaid balance is exhausted.

Policies

Prepaid Gating
Usage is gated by the prepaid account balance rather than a hard rate cap.
Backoff Strategy
Clients should implement retries with exponential backoff and honor Retry-After on 429.
Volume Onboarding
High-volume messaging and calling is arranged with 46elks support for capacity and deliverability.

Sources