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.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/notificationapi-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.