API Usage Guidelines
While the WorqHat API currently does not enforce strict rate limits, we recommend following these best practices to ensure optimal performance and reliability for all users.Automatic Retries
The official WorqHat JavaScript/TypeScript library automatically handles retries for certain types of errors. By default, the library will retry failed requests up to 2 times with an exponential backoff strategy.What Gets Retried
The following types of errors are automatically retried:- Connection errors (network connectivity problems)
- 408 Request Timeout errors
- 409 Conflict errors
- 429 Rate Limit errors
- 500+ Internal Server errors
Configuring Retries
You can configure the retry behavior using themaxRetries
option:
Request Timeouts
Requests to the WorqHat API time out after 1 minute by default. You can configure this timeout period to better suit your applicationβs needs.APIConnectionTimeoutError
is thrown. Note that requests which time out will be retried according to your retry configuration.
Python Library Retries
The official WorqHat Python library also includes automatic retry functionality similar to the JavaScript library. By default, it retries certain errors 2 times with exponential backoff.Custom Retry Logic
If youβre using a language without an official WorqHat library, we recommend implementing similar retry logic in your API client:Monitoring Your API Usage
While we donβt currently enforce strict rate limits, we do monitor API usage patterns to ensure the stability and performance of our platform. If we detect unusual or potentially harmful usage patterns, we may reach out to you to discuss your use case and find a solution that works for everyone.Future Considerations
As our platform grows, we may introduce rate limits to ensure fair usage across all customers. We will provide advance notice of any changes to our API usage policies.Need Help?
If you have questions about API usage or need higher throughput for your application, please contact our support team.