You're correct about the 50,000 submission cap for webhook tables. [1]
Regarding rate limits: our webhook throughput limit is 10 webhooks per second. [2] That translates to 600 per minute or 36,000 per hour if you're sending continuously at that rate.
You're right—there are two types of limits for webhooks:
1.
Rate limit: 10 webhooks per second (600 per minute). [1]
2.
Total submissions cap: 50,000 submissions per webhook table. Once you hit this limit, you'll need to create a new webhook table to continue receiving data. [2]
When pushing 1500 webhooks rapidly, you likely exceeded our 10 webhooks per second throughput limit. [1]
To fix this, add delays between submissions—at least 100ms between each webhook to stay under the rate limit.
Also verify your endpoint URL is correct and that your server is sending successful (2xx) HTTP status codes in response. [2] Acknowledge receipt of the webhook immediately before processing data to avoid timeouts. [3]
If errors persist after adjusting your rate, click into the specific cells showing errors in your webhook table to see more details about what's failing.
You're absolutely right. When sending large volumes of webhooks, batching is the best approach.
The key is respecting the 10 webhooks per second rate limit—this means adding at least 100ms delay between each submission. [1]
For your 1,500 webhooks, consider breaking them into smaller batches (e.g., 100-200 at a time) with proper delays between each webhook. This prevents overwhelming the processing capacity and reduces failed submissions.
Also keep in mind that webhook tables have a 50,000 total submission limit. [2] Once reached, you'll need to create a new webhook table to continue receiving data.
If you still need help managing your webhook volume or have other questions, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?
