Rate Limits
The Tailwind API limits each organization to 10,000 requests per day. Every API key and every OAuth connection in the organization, including MCP clients such as ChatGPT and Claude, counts toward the same limit. The counter resets at midnight UTC.
There is no separate per-second request limit. Scheduling actions also use the limits or credits included with your Tailwind plan.
Rate Limit Exceeded
Section titled “Rate Limit Exceeded”After an organization reaches its daily limit, its requests receive a 429 Too Many Requests response:
{ "error": { "code": "RATE_LIMIT_EXCEEDED", "message": "Daily rate limit of 10000 requests for this organization exceeded. Resets at midnight UTC." }, "meta": { "requestId": "abc123" }}The response includes a Retry-After header with the number of seconds until the limit resets. Retrying before then will continue to return 429.
Pinterest Rate Limits
Section titled “Pinterest Rate Limits”Pinterest also limits how often each connected Pinterest account can be read or changed. When Pinterest refuses a request for that reason, the API answers 503 Service Unavailable with reason set to pinterest_rate_limited, never 429:
{ "error": { "code": "SERVICE_UNAVAILABLE", "message": "Pinterest is rate limiting analytics requests for this account. Retry in a few minutes.", "reason": "pinterest_rate_limited" }, "meta": { "requestId": "abc123" }}This limit belongs to one Pinterest account, not to your organization. Retry that request in a few minutes, and keep making other requests as usual. Analytics and Pin inventory requests also include a Retry-After header with the seconds until Pinterest’s limit resets, when Pinterest reports it.
Best Practices
Section titled “Best Practices”Cache Read Responses
Section titled “Cache Read Responses”Cache data that does not change frequently, such as accounts and boards:
// Boards rarely change; cache them for five minutes.const boards = await getCachedOrFetch('boards', 5 * 60 * 1000, () => fetch(`${API_URL}/v1/accounts/${accountId}/boards`, options));Avoid Unnecessary Requests
Section titled “Avoid Unnecessary Requests”- Reuse account and board IDs instead of looking them up before every post.
- Follow the
cursorreturned by list endpoints and stop when it isnull. - Do not retry validation, authentication, or not-found errors without changing the request.
Monitor Usage
Section titled “Monitor Usage”In Tailwind, open Settings > API Access and view an API key’s usage. The page shows that key’s request history and today’s request count across your whole organization against its limit.
Increasing Your Limit
Section titled “Increasing Your Limit”If 10,000 requests per day is not enough for your organization, contact support@tailwindapp.com with your organization name, use case, and expected request volume.
