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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-01.
Written by API Evangelist on 2026-07-01 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/notificationapi-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.