ComRaidComRaid Docs

Rate limits

Request quotas, send capacity, and retry guidance.

Operational rate limits protect public API and mobile endpoints. Limits are fixed operational safeguards (not plan tiers or billing quotas). Over the limit, the API returns 429 with Retry-After.

Send capacity

One worker is sized to target about 10,000 Provider sends per second for a single Project (FCM's per-project quota), with a per-Project token bucket and batched Delivery status writes. The measured end-to-end figure on a production-sized Railway service is pending load test — Docs will state that number when the run is recorded (never "millions"). Multi-worker scale-out is later.

Overview

ComRaid applies Redis-backed fixed-window rate limits:

  • Public product API (API key): scoped per API key. Contact routes and the remaining product routes (/messages, /campaigns, /segments, /media) each use their own bucket.
  • Mobile SDK (publishable X-ComRaid-App-Id): scoped by project and client IP.
  • Default window is 1m unless noted.

Dashboard session APIs have separate auth and import limits; they are not listed here.

Public API (API key)

Per API key, per one-minute window. Two keys never share a bucket. Limits are configurable by ComRaid (env), not per plan.

Route groupPathsDefault limit
Contacts/contacts, /endpoints, contact opt-outs and preferences300 / min
Messages/messages300 / min
Campaigns/campaigns300 / min
Segments/segments300 / min
Media/media60 / min

Media uploads use a tighter bucket so a single key cannot flood object storage. Message creates and sends share the Messages bucket.

Mobile endpoints

Default limits per project + IP, per one-minute window:

MethodPathLimit
GET/mobile/notification-categories120 / min
POST/mobile/subscriptions30 / min
POST/mobile/subscriptions/{id}/token30 / min
POST/mobile/subscriptions/{id}/session6 / min
POST/mobile/subscriptions/{id}/login20 / min
POST/mobile/subscriptions/{id}/logout30 / min
POST/mobile/subscriptions/{id}/opt-out30 / min
POST/mobile/subscriptions/{id}/opt-in30 / min
PUT/mobile/subscriptions/{id}/attributes30 / min

Token rotation shares the subscribe bucket (30 / min). Session has its own bucket (6 / min; the SDK calls it at most once per foreground, debounced to about every 30 minutes). Login is stricter (20 / min). Product API key routes and Dashboard session APIs are not covered by these mobile limits.

Delivery acknowledgements

Delivered and opened acknowledgements are limited to 300 / min per App ID and IP. Full request and response schemas for every Mobile operation live in the API Reference.

Over-limit response

When a limit is exceeded, the API returns 429 with code rate_limited and a Retry-After header (seconds remaining in the window).

HTTP/1.1 429 Too Many Requests
Retry-After: 42
Content-Type: application/json

{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Retry after 42 seconds.",
    "request_id": "hostname/abc123-000001"
  }
}

If the limiter itself is temporarily unavailable, the API returns 503 with code service_unavailable. Retry with backoff; the SDKs do this for you.

See Errors for the shared error shape and status codes.

On this page