NotificationAPI · Rate Limits

Notificationapi Rate Limits

NotificationAPI enforces per-account request rate limits on the REST API and bounds notification throughput by the monthly active user (MAU) and notification-volume allowances of the account's plan. Downstream channel providers (email, SMS, push) impose their own throughput ceilings. Specific per-endpoint request-per-second values are not published and are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring requests, users, notifications, and messages.

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

Tagged areas include Notifications, Messaging, Email, SMS, and Push.

5 Limits Throttle: 429
NotificationsMessagingEmailSMSPushIn-App InboxRate LimitingQuotasThrottling

Limits

REST API Requests account
requests
see provider documentation
Per-account request rate limit across the REST API; raises by plan tier.
Monthly Active Users (MAU) account
users
per plan allowance
Notification throughput is bounded by the plan's MAU allowance.
Notification Volume account
notifications
per plan allowance
Monthly notification-volume allowance per plan; overage may be metered or blocked.
SMS / Voice Throughput account
messages
downstream provider limits
SMS and voice throughput is subject to carrier and downstream provider limits.
In-App Inbox Reads user
requests
see provider documentation
Applies to GET /users/{userId}/notifications/INAPP_WEB used by the in-app inbox.

Policies

Tiered Limits
Rate limits and MAU / volume allowances rise from Free to Startup, Business, and Enterprise.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources