Skip to main content
Question

Figma API Rate Limit Issue During Integration with DhiWise

  • March 31, 2026
  • 1 reply
  • 13 views
mohitchavda

Hi Figma Support Team,

We are currently experiencing an issue related to Figma API rate limits while importing designs into DhiWise. The error displayed is:
“Figma’s API rate limit reached. Please try again after few minutes.”

This issue is occurring frequently and is impacting our development workflow. We would like to understand:

  • What are the current API rate limits for our account/workspace?

  • Are there any ways to increase the limit or optimize usage?

  • Any best practices to prevent hitting the rate limit during integrations like DhiWise?

Kindly guide us on how to resolve or manage this issue effectively.

Looking forward to your support.

Thanks & Regards,
Mohit

1 reply

ksn
Figmate
  • ksn
  • Community Support
  • April 6, 2026

Hi ​@mohitchavda - thank you for inquiring. If I’m understanding your core issues with the limits, it may be due to request patterns rather than a hard limit.

Limits aren’t defined at a workspace level — they depend on:

  • Seat type (Viewer/Collab vs Dev/Full) & also the plan of the file being accessed.-- see here for details.

Additionally, here is the developer documentation: https://developers.figma.com/docs/rest-api/rate-limits/

A few things to check:

  • Auth model - shared personal access tokens will hit limits faster than OAuth (limits are per user)

  • Request patterns - repeated GET /files/:key calls and lack of caching are common causes during imports

Some things to try:

  • Don’t retry right away - give a little bit of time to to things to settle + avoid repeatedly calling the API in short intervals
  • Save cached file data instead of fetching it over and over
  • Combine requests instead of making lots of small ones

I will note that I’m a little less versed when it comes to API calls, so I may not have interpreted your original asks. If that’s the case, please let me know.

 

Terms & ConditionsCookie settingsAccessibility statement