Documentation: API Rate Limits
in progress
serge.george
User Story:
As a developer integrating Taskade’s API,
I want to know the exact rate limits applied to API requests,
So that I can optimize my workflows and avoid unexpected throttling or errors.
Current Issue:
While retrieving a structured list of all my AI agents across all workspaces, I encountered API rate limits, forcing me to introduce artificial delays to prevent failures.
The workflow I used:
- Retrieve all my workspaces via the API.
- For each workspace, fetch all folders.
- For each folder, fetch all AI agents within it.
This recursive approach resulted in multiple API calls in succession. However, at a certain point, requests started failing due to rate limits. Since these limits are not documented, I had to experiment by adding delays between requests to avoid hitting them, making the process inefficient.
Proposed Solution:
Provide clear documentation on API rate limits, including:
- Maximum requests per minute/hour.
- Behavior when the limit is exceeded (e.g., error codes, retry headers).
- Recommended best practices for handling rate limits gracefully.
Log In
John at Taskade
This is a completely fair ask — hitting unexpected rate limits while building an integration is frustrating, especially when the only signal is a failed request and there's no published limit to design around. Introducing artificial delays without knowing the actual thresholds is not a sustainable engineering approach.
Documenting exact rate limits (requests per minute/hour, per endpoint, per workspace) with appropriate response headers (X-RateLimit-Limit, X-RateLimit-Remaining, Retry-After) is standard API practice, and this is something we need to deliver for developers building on top of Taskade.
Your specific use case — enumerating all AI agents across all workspaces — is a legitimate batch operation that should be clearly documented with expected throughput guidance.
Improved API documentation, including rate limit specs and pagination best practices, is on our roadmap. We appreciate the detailed user story format — this is exactly what helps us write better docs. We'll update this thread when rate limit documentation goes live. In the meantime, a conservative rate of 1 request/second generally keeps you safe. Thanks for flagging this!
John at Taskade
Update: We're actively working on this!
This is in development and your votes helped us prioritize it.While you wait, check out what's new:
- **Taskade Genesis** — generate AI-powered apps, agents, and workflows
- **Community Hub** — 1000+ free templates and apps
Follow our progress: Changelog | Product Updates
Thanks for your patience and for helping shape Taskade!
John at Taskade
marked this post as
in progress
Update: We've shipped Public API v2!
Rate limit documentation and developer guides are being expanded. Check our API docs for the latest information.In the meantime, explore what's new:
- Build with Taskade Genesis — AI-powered app builder
- Browse Community Templates — 1000+ free templates
Follow our progress: Changelog | Product Updates