Skip to main content
Question

Figma API rate limit triggered repeatedly after failed sync – blocking workflow

  • March 30, 2026
  • 3 replies
  • 24 views
SDT

Hello,

 

I’m reaching out regarding a recurring issue with Figma API rate limits that is currently blocking my work.

 

I’m using a Professional plan.

 

I was working with a third-party integration (Useberry) to sync a prototype. However, the sync was not working from the beginning — the prototype wouldn’t sync at all.

 

After several retry attempts, I received a Figma API rate limit error with a cooldown of over 30 hours. Later, the issue repeated, and now I’m facing another cooldown of around 100 hours, which is still ongoing.

 

The key issue is that:

- the sync was already failing before any rate limit was triggered  

- repeated cooldowns are now preventing any further work  

- I’m unable to proceed with launching a time-sensitive research study  

 

Could you please help clarify:

- why the sync might have been failing initially  

- why such long cooldowns are being applied  

- whether it’s possible to lift or reset the current API rate limit  

- how to safely use integrations like Useberry without triggering this behavior  

 

This situation is critically blocking my workflow, so I would really appreciate your help.

 

Thank you,  

Kristina

    3 replies

    djv
    Figmate
    • djv
    • Community Support
    • March 31, 2026

    Hi ​@SDT, thanks for reaching out! 

    I completely understand how this must be slowing down your workflow. Since you mentioned that the prototype wouldn’t sync at all, it may be best to work with Useberry support directly to first ensure your Figma integration is set up correctly. You can fill out a support contact form here.

    From there, if you’d like to reference them, our Rest API limits are listed here. You may want to keep these in mind as you’re working in the future. 

    SDT
    • SDT
    • Author
    • New Member
    • April 2, 2026

    Useberry Support referred me to you. 

    djv
    Figmate
    • djv
    • Community Support
    • April 2, 2026

    Hi ​@SDT, thanks for letting us know! 

    That’s very odd. I understand your sense of urgency here, but third party integrations typically provide support directly to their users.

    Did you run into any issues authorizing Useberry to connect with Figma? Did you ensure your Figma prototype was public before attempting use? Did you make any edits to your prototype?

    Any of the following could have disrupted your sync. Support is not able to life or reset your API rate limits, but when requests are getting rate-limited, we recommend:

    • Review the rate limit table and check the tier of the rate-limited endpoint. Also check the X-Figma-Rate-Limit-Type value in the 429 error returned when the endpoint is rate-limited. The table, endpoint tier, and rate limit type will help you identify why a given user is encountering rate limits.
    • Batch requests whenever possible. For example, suppose you have an app that downloads images from a Figma file. Instead of sending individual requests for each image, you’d want to send a single request that includes a list of all the node ids you want to download as images.
    • Cache results. Rather than sending frequent requests, such as a new requests whenever a part of an app’s UI is navigated to, instead cache the data from an earlier request. Then, either refresh the data when requested (such as when a user explicitly wants to refresh data in the app UI), or on a periodic basis that fits the rate limits.
    • Make sure your app is correctly handling rate-limited requests. Make sure your app gracefully retries user requests after the Retry-After value in the 429 error.

     

    My team here on the forum isn’t able to help with the Useberry integration, but I hope this information is at the very least, helpful in terms of better understanding and navigating your rate limits. 

    Terms & ConditionsCookie settingsAccessibility statement