Skip to main content
Question

API Rate Limit Issue – 429 Too Many Requests on Free & Paid Plan

  • June 7, 2026
  • 1 reply
  • 18 views
ajain1

Hi Figma Support Team,

I hope this message finds you well. I am writing to report a persistent issue I have been encountering while integrating with the Figma API.

**Issue Summary:**
I am consistently receiving a 429 Too Many Requests error when calling the Figma API. This issue occurs on both my Free plan and Paid plan accounts, which is unexpected — especially on the paid tier.

**Details:**
- Error: 429 Too Many Requests
- Affected Plans: Free and Paid
- API Endpoints affected
- Frequency: occurs every time while calling api

**What I have tried:**
- Reducing the frequency of API calls
- Adding delays/throttling between requests
- Using different API tokens on both plans

Despite these efforts, the issue persists. I would like to understand:
1. What are the exact rate limits for Free and Paid plans?
2. Is there a recommended retry strategy or backoff mechanism?
3. Are there any higher-tier API access options or enterprise quotas available?

I would appreciate your guidance on resolving this at the earliest. Please let me know if you need any additional information such as logs, request headers, or account details.

Thank you for your support.

Best regards,

Atul Jain
[PII redacted by moderator]

1 reply

adamsmasher
Figmate

Hi, ​@ajain1! Thanks for your post - appreciate all the detail you included. 

 

Are you referring to the REST API, or the Figma MCP server. I’m guessing it’s the former from what you are describing. Either way, the following two articles from our Developer documentation site cover rate limits of all seat types for both:

 

With the REST API, the 429 error should have the following fields with it that will give you a bit more information to work with:

"Retry-After": Integer
"X-Figma-Plan-Tier": String enum
"X-Figma-Rate-Limit-Type": String enum
"X-Figma-Upgrade-Link": String

Those will help you know which limit tier you are hitting and when you can hit it again; ideally with that you can further identify what call is specifically doing it, that way you can refactor it to hit the API less often. This is covered more in depth in the article above, but in general you want to batch your requests whenever possible, cache results, and have properly handling of 429 errors so it can retry them gracefully. Reducing the frequency like you’ve done is good, but batching and caching will help as well.

 

Let me know if you have any questions!

Terms & ConditionsAccessibility statement