Skip to main content
Question

429 Error Handling

  • November 19, 2025
  • 2 replies
  • 758 views
Mikhail E.

I'm working on gracefully handling 429 errors when fetching Figma files in our app. To import a Figma layout, users provide an X-FIGMA-TOKEN. Recently, the rate limits have been updated, and we need to provide more detailed information about the current user's limit. However, the response I receive from the endpoint does not include any of the headers described in the developer documentation. The response only contains the status code and a message.

Am I missing something? How can I access the Retry-After, X-Figma-Rate-Limit-Type, and other headers described here: https://developers.figma.com/docs/rest-api/rate-limits/?

I use the fetch method the request looks something like this:

 

fetch(`https://api.figma.com/v1/files/${file}/nodes?ids=${node}&geometry=paths`, { headers: {'X-FIGMA-TOKEN': KEY, 'Content-Type': 'application/json'} })

 

This is the response I get: {status: 429, err: 'Rate limit exceeded'}
The response headers are empty.
 

2 replies

shijia.me
  • shijia.me
  • Active Member
  • November 19, 2025

I'm working on gracefully handling 429 errors when fetching Figma files in our app. To import a Figma layout, users provide an X-FIGMA-TOKEN. Recently, the rate limits have been updated, and we need to provide more detailed information about the current user's limit. However, the response I receive from the endpoint does not include any of the headers described in the developer documentation. The response only contains the status code and a message.

Am I missing something? How can I access the Retry-After, X-Figma-Rate-Limit-Type, and other headers described here: https://developers.figma.com/docs/rest-api/rate-limits/?

I use the fetch method the request looks something like this:

 

fetch(`https://api.figma.com/v1/files/${file}/nodes?ids=${node}&geometry=paths`, { headers: {'X-FIGMA-TOKEN': KEY, 'Content-Type': 'application/json'} })

 

First, check your response status code is 429.

Then, get these info from the response header.

Marcello Cultrera

​@Mikhail E. please find below an alternative workaround to Figma 429 rate limits as well reducing weight on Figma infrastructure. This as an immediate fix.

The issue isn’t Figma’s limits themselves (which are more recently conservative and problematic), it’s the way large /v1/files/:key?ids=… calls pull entire subtrees (often megabytes), then trigger dozens of image requests when frames have 50-200 children. That burst pattern quickly hits Figma’s limits protection causing 4-5 day lockouts.

A proposed solution is to stop fetching everything upfront and adopt a metadata‑first, prune‑first, fetch‑last pipeline:

  1. Fetch only component metadata.
  2. Pre‑filter locally to remove hidden frames, junk nodes and remote libraries.
  3. Fetch a pruned node tree with limited depth (depth=2–3) to keep responses <500 KB.
  4. Do code analysis and token extraction locally without extra API calls.
  5. Fetch images only for the final deduplicated list, in small adaptive batches with exponential backoff.

This reduces jobs from 10+ calls and multi‑MB traffic down to 2–3 calls and <500 KB, eliminating 429 errors even on complex frames.

This is a significant architecture refactor but worked for us at canvaseight.io and at codeFlow Lab - so worth checking if you currently already follow this pattern or if making these changes solves your rate limits problem. Ultimately it should benefit lowering the impact on Figma API infrastructure.

Best regards,
Marcello

!--endfragment>

 

Terms & ConditionsCookie settingsAccessibility statement