.svg?alt=media&token=4dcba59f-0ed4-402a-88ba-6a9fa420bacf)
Rate Limits
To ensure fair usage and maintain the quality of our service, the Dashworks API implements rate limiting. This page explains our rate limit policies and how to handle them in your applications.
Rate Limit Details
The following are key points about our rate limits:
Endpoint Limit:
The
/v1/answerendpoint is limited to 1 request per minute.The
/v1/documentsendpoint has different limits based on the method used.PUT:20 requests per minute.GET:60 requests per minute.DELETE:60 requests per minute.
Reset Interval: Rate limits reset on the minute mark, regardless of when the request was made within that minute.
Limit Exceeded: A 429 (Too Many Requests) response is sent when you hit the rate limit.
Scope: Rate limits apply at the Dashworks workspace level, shared across all API keys and bots.
Reset Timing Example
If you make a request at 10:14:01, the next available request slot will be at 10:15:00.
If you make a request at 10:14:59, the next available request slot will still be at 10:15:00.
We may adjust the reset timing in the future. Always refer to the latest documentation for the most up-to-date information.
Workspace-Level Limits
It's important to understand the implications of workspace-level rate limits:
All API keys associated with your workspace share the same rate limit.
Creating additional API keys will not increase your request throughput.
The same limit applies to all bots within your workspace.
Best Practices
To make the most of the Dashworks API while respecting rate limits:
Implement retry logic with exponential backoff for 429 responses.
Consider caching responses where appropriate to reduce API calls.
Design your application to distribute requests evenly over time.
Monitor your API usage to stay within the limits.
Need Higher Limits?
If you require higher rate limits for your use case, please contact our support team to discuss your needs and potential solutions.
Last updated