How Is Rate Limit Counted for Node ID Requests vs Whole File Requests?

Question

Hi team 👋,I’m looking for clarification on how API rate limits are calculated when requesting specific node IDs compared to fetching the entire file.Questions:	When calling the /nodes endpoint with multiple node IDs, does it count as:			a single API request regardless of the number of node IDs, or						multiple requests internally that affect rate limits?					Is there any difference in rate-limit cost or weighting between:			fetching the whole file, and						fetching a subset of nodes?					Do factors like number of node IDs, file size, or response payload size influence how rate limits are counted?

Wirkkarl · Answer

Hi team 👋,I’m looking for clarification on how API rate limits are calculated when requesting specific node IDs compared to fetching the entire file.Questions:When calling the /nodes endpoint with multiple node IDs, does it count as:a single API request regardless of the number of node IDs, ormultiple requests internally that affect rate limits?Is there any difference in rate-limit cost or weighting between:fetching the whole file, andfetching a subset of nodes?Do factors like number of node IDs, file size, or response payload size influence how rate limits are counted?Hey Ankit,From what I’ve seen, Figma counts each API call you make, not the number of node IDs inside it. So if you request multiple node IDs in one /nodes call, it usually counts as just one request toward your rate limit.Fetching the whole file vs. a subset of nodes doesn’t change the request count, but bigger files or responses might take longer to process. It’s more about performance and possible timeouts than actually hitting the rate limit.So in short: pack as many node IDs as you can in a single request—it won’t cost extra, but just be mindful of very large responses.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded