Overview
Rate Limits
If you exceed that limit we'll return a 429 HTTP status code to you.
Overview of Request Costs
| Tool | Request Cost |
|---|---|
| Domain Search | From 1 to 10 Emails |
| Email Finder | Counted as 1 |
| Author Finder | Counted as 1 |
| Enrichment | Counted as 1 |
| LinkedIn Email Finder | Counted as 1 |
| Email Verifier | Counted as 1 |
| Phone Search and Validate | Counted as 1 |
requests
No requests are counted if Tomba cannot provide an email.
Overview of Bulks Limits
| Tool | Limit |
|---|---|
| Bulks Domain Search | 15/d |
| Bulk Email Finder | 15/d |
| Bulk Author Finder | 15/d |
| Bulk Email Enrichment | 15/d |
| Bulk Email Verifier | 15/d |
| Bulks Phone Search and Validate | 15/d |
Additional Notes:
- When a Domain Search or an Email Finder request doesn't return a result, the request isn't counted. Similarly, for the Email Verifier: if you verify a webmail and no result is provided, the request will not be used.
- Unique requests are counted only once every 30 days against your quota. If you need to re-run a series of requests due to improper data storage or for any other reason, these will not count against your monthly quota. Consequently, you can make identical API requests repeatedly within the same billing period. This flexibility is especially beneficial for developers who are testing integrations.
Is There a Request Per Second Limit?
Understand if there's a limit on requests per second, ensuring you can manage your searches efficiently without exceeding platform constraints.
Request Rate Limits
| API Endpoint | Rate Limit |
|---|---|
| Email Finder | 300 requests per minute |
| Enrichment | 300 requests per minute |
| Author Finder | 150 requests per minute |
| LinkedIn Email Finder | 100 requests per minute |
| Email Verifier | 150 requests per minute |
| Domain Search | 15 requests per second |
limit
If you reach the limit, a 429 error will be triggered.