The number of requests the API consumer can make in a second
A rate limit is the number of API requests (calls) an app or user can make within a defined time.
If the number of requests exceeds the limits described in the table below, requests are temporarily blocked (throttled) until the rate limit window resets; the responses return an error with status code 429.
The methods not listed in this table share a total default rate limit of 200 requests per second.
NoteThere is no IP allowlist or firewall requirement for API access ā you don't need to whitelist any IP addresses on your side to call the API.
| Method | Request type | Endpoint | Max requests per second |
|---|---|---|---|
| Get contact ID by token | GET | /api/v1/contact/token/{app_uuid}/{token_id}/contactId | 150 |
| Search for contacts | GET | /api/v1/contacts | 50 |
| Generate events v1 | POST | /api/v1/event | 350 |
| Generate past events V1 | POST | /api/v1/past_events | 100 |
| Delete events | DELETE | /api/v1/past_events | 5 |
| Update interaction status | PUT | /api/v1/interactions/{interaction_id}/status | 300 |
| Get contact's message history | GET | /api/v2/contacts/messages | 10 |
| Generate event v2 | POST | /api/v2/event | 350 |
| Generate past events V2 | POST | /api/v2/past_events | 100 |
| Get email message | GET | /api/v1/messages/email/{id} | 10 |
| Generate event v3 | POST | /api/v3/event | 350 |
| Generate past events V3 | POST | /api/v3/past_events | 100 |
Hourly limit on single email sends
In addition to the per-second request limits, each account has an hourly limit on single (one-off) email sends ā 100 emails per hour by default. The limit applies to email messages sent by workflow message blocks and by the Send prepared message and Send Email message API resources. Bulk campaigns are not affected.
When the limit is exceeded, the API returns a 403 error Per hour emails limit reached: N, where N is the current limit value. The same error is displayed in the workflow launch history. Sends rejected over the limit fail and are not retried automatically.
To increase the limit for your account, contact support.
Telegram broadcast throughput
Telegram controls bot delivery limits separately from eSputnik API request limits. For free broadcasts, Telegram recommends keeping bulk notifications at approximately 30 messages per second per bot; exceeding the limit can produce 429 responses. At that rate, 500,000 messages require at least about 4 hours 38 minutes, and actual delivery can take longer.
Telegram also offers paid broadcasts with higher limits for eligible bots. See the current Telegram Bot FAQ before planning a large send.