TL;DR: Figma's REST rate limits are tiered, not flat. Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much looser. On a 429, honor the Retry-After header; for severe violations it can be multi-day, so back off instead of hammering.

## Fix
1. Figma's REST rate limits are tiered, not flat.
   Expected: this specific failure stops.
2. Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much looser.
   Expected: this specific failure stops.
3. On a 429, honor the Retry-After header; for severe violations it can be multi-day, so back off instead of hammering.
   Expected: this specific failure stops.
4. The limit follows the plan containing the file, so a paid seat elsewhere does not raise the quota on a Starter file.
   Expected: this specific failure stops.

## Details
Figma's REST rate limits are tiered, not flat. Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much looser. On a 429, honor the Retry-After header; for severe violations it can be multi-day, so back off instead of hammering. The limit follows the plan containing the file, so a paid seat elsewhere does not raise the quota on a Starter file.

## When to use
You hit exactly this: Figma rate limits are tiered and follow the file's plan, not your seat in Figma.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Figma (versions mentioned here: v1).

## Root cause
Practical defenses: narrow reads with ids and depth params instead of full-file pulls, cache component and style metadata, and never treat the REST API as a way around Figma quotas.