To enhance platform stability, optimize performance, and ensure consistent service quality for all users, Bigdata.com will introduce official rate limits on our public search services starting Monday, November 16th, 2026.
To prevent disruptions to your workflows and integrations, please have your engineering or technical team implement the following practices prior to November 16th:
- Handle HTTP 429 Status Codes: Ensure your client applications gracefully catch 429 responses rather than failing silently or crashing downstream processes. - Respect Retry-After Headers: Responses returning status code 429 will include a Retry-After HTTP header specifying the backoff duration. Your systems should wait for the designated interval before attempting another request. - Implement Exponential Backoff & Jitter: Incorporating an exponential backoff strategy with randomized jitter for retry loops will help smooth out traffic spikes and minimize rejected calls.
If you have questions about specific limit thresholds, integration best practices, or need assistance reviewing your current traffic volumes, please contact our support team at [support@bigdata.com] or reach out directly to your account representative.
Posted Nov 06, 2026 - 10:19 UTC
This scheduled maintenance affects: Bigdata API (Document Processing API, Knowledge Graph API, Research Agent API, Search API, Structured Data API).