To ensure optimal performance and fair usage for all users, the Precept API enforces rate limits. Understanding these limits will help you design your integration for maximum efficiency. Our limits are based on three factors: rate, volume, and concurrency.
- Rate: The number of API requests you can make per minute.
- Volume: The total number of items (e.g., leads or companies) you can process per minute.
- Concurrency: The number of items that can be processed simultaneously.
Leads Enrichment
The /leads/enrich endpoint is designed for high-throughput contact enrichment. Here are the limits:
| Limit Type | Value |
|---|
| Rate Limit | 30 requests per minute |
| Volume Limit | 1,000 leads per minute |
| Max Batch Size | 1,000 leads per request |
Optimizing for Speed
To maximize your enrichment speed, we recommend sending as many leads as possible in each batch, up to the 1,000-lead maximum. Since the volume limit is 1,000 leads per minute, you can send one batch of 1,000 leads to reach the maximum throughput within a minute.
Concurrency Queue
Each workspace has a default queue size of 100 concurrent enrichments. This means up to 100 of your contacts are processed in parallel at any given time.
If you submit a batch of 1,000 leads, the first 100 will begin processing immediately. The remaining 900 will wait in a queue. As each enrichment finishes, the next lead from the queue will automatically start processing until the entire batch is complete.
Company Insights
The /companies/insights endpoint has its own set of limits:
| Limit Type | Value |
|---|
| Rate Limit | 100 requests per minute |
| Volume Limit | 5,000 companies per minute |
| Max Batch Size | 5,000 companies per request |
Important: If you are finding contacts of decision-makers with includeContactDetails: true in your Company Insights request, the number of decision-makers will count towards your Leads Enrichment rate and volume limits.
