Understand OneSignal’s API and application rate limits, including per-endpoint thresholds and messaging limits based on your subscribed user count. Learn how to avoid triggering limits and what to do if your app is disabled.
Endpoint | Rate Limit |
---|---|
Create notification | Free plans: 150 requests/sec/app Paid plans: 6,000 requests/sec/app Each request can target multiple users or audiences. |
Creating, updating, or deleting users or subscriptions | 1000 requests/sec/app 1 request/sec/user or subscription Up to 100 property modifications per request. |
View messages, View templates, View user, View message | 1 request/sec/app 10 requests/sec look-back. |
Message History, Audience Activity CSV | Please keep parallel request sizes under 100 GB per file. |
429
response:
Retry-After
header with the number of seconds to wait before retrying. Monitor your app’s API usage patterns and implement exponential backoff when handling 429 errors.
Example dashboard banner to re-enable your app when hitting the application rate limit.
support@onesignal.com
for assistance.
Scenario | Rate Limit Triggered? |
---|---|
1 notification to 1,000 users | ❌ No |
10 notifications to 1,000 users each | ✅ Yes (10 × 1,000 = 10,000) |
10,000 notifications to 1 user each | ✅ Yes |
9 notifications to 1,000 users in 14 minutes, then 1 more after 1 minute | ❌ No (new 15-min window) |
9 notifications to 1,000 users in 14 minutes, then 9 more after 1 minute | ❌ No (static 15-min windows) |
429
), but apps are not disabled.
support@onesignal.com
for assistance.
support@onesignal.com
for assistance.