Rate limits

Rate limits protect the people you contact and your balance. Calls have one limit: the number of calls in progress at the same time. Texts count per organization, over rolling time windows.

Default text message limits

Window Text messages
Per minute 300
Per hour 3,000
Per day 20,000
Per destination number, per day 50

Releases of numbers bought from Resia have their own limits per hour and per day. Resia has no daily limit for 10DLC brand registrations or campaign submissions. Provider restrictions and fees apply.

Your organization can have different limits. Read the limits that apply to you:

curl --fail-with-body --silent --show-error \
  "$RESIA_API_BASE/v1/rate-limits" \
  --header "Authorization: Bearer $RESIA_API_KEY"

The response has call, message, phone_number_release, ten_dlc, and fullplex sections. A limit of 0 means the action is blocked. The ten_dlc.per_day value is null, which means no daily submission limit.

To raise a limit, contact support@resia.ai.

Concurrent calls

Your organization has a limit for calls in progress at the same time. Inbound and outbound calls share this limit. One call uses one slot, also when it has additional participants.

The call section of the response shows two values:

Field Meaning
concurrent The most calls that can be in progress together. 0 stops new calls.
in_progress The calls in progress now. This count can be above concurrent after a decrease of the limit. Those calls continue.

At the limit, Resia does this:

  • POST /v1/calls gets 429 with the code rate_limited. The message gives the limit. This response has no Retry-After header, because Resia cannot know when a call will end. Try again after a call ends.
  • A batch call stays queued until a slot is free.
  • A new inbound call rings out. Resia does not send the call.incoming webhook, and it creates no call record and no charge.
  • A new call from an orchestration run is refused with the same message.

A person who calls your numbers many times can fill your slots. To raise the limit, contact support@resia.ai. Every organization has 10 slots included. Slots above those have a monthly charge. See Billing.

When you reach a limit

At a phone number release limit, a request such as DELETE /v1/phone-numbers/{phone_number} gets 429 Too Many Requests and a Retry-After header with the number of seconds to wait. A single text send gets the same answer at a text message limit:

HTTP/1.1 429 Too Many Requests
Retry-After: 41

{
  "error": {
    "code": "rate_limited",
    "message": "This organization is limited to 2 phone number releases per day. Try again in about 41 seconds.",
    "request_id": "01K3..."
  }
}

Wait for Retry-After before you try again. If more than one window is full, the header gives the longest wait.

A 429 with the code temporarily_unavailable is different. It means Resia is short of capacity for a moment, not that you reached your own limit. Retry after a short wait.

Batches do not hit 429s

Call batches queue their calls and dial them as your concurrent call limit allows. Text message batches send at the pace your text limits allow. Use a batch when you have many calls or texts to send. A text message batch gets 429 only if it is larger than your queued-text limit.

Orchestration runs

Orchestration runs have no separate organization limit. Their calls count against the concurrent call limit, and their texts against the text limits. Each run also has its own max_calls, max_messages, and max_spend_in_cents.

Fullplex sessions

The fullplex block reports concurrent_sessions and in_progress. The default is five concurrent sessions per organization. When Fullplex is unavailable, its routes return 503 with unavailable. Contact support for availability. A zero limit blocks new sessions. See Live API.