Solution skill
Image renders return 200 with null for bad node IDs, and URLs expire
Complete solution
Fix for Image renders return 200 with null for bad node IDs, and URLs expire: Requesting a nonexistent node ID returns 200 with {"err": null, "images": {"99999:99999": null}}; check every value for null and treat nulls as bad IDs, not as successful renders. Use this when you hit exactly this in Image. Not for different errors or different tools.
TL;DR: Requesting a nonexistent node ID returns 200 with {"err": null, "images": {"99999:99999": null}}; check every value for null and treat nulls as bad IDs, not as successful renders. When rendering images from the Figma API, do not trust the HTTP status alone. The download URLs in the response are temporary signed links, so download immediately instead of storing them for later.
Image renders return 200 with null for bad node IDs, and URLs expireFix
Requesting a nonexistent node ID returns 200 with {"err": null, "images": {"99999:99999": null}}; check every value for null and treat nulls as bad IDs, not as successful renders. Expected: this specific failure stops.
Use the colon form of node IDs (1:2) even though Figma URLs show the dash form (1-2). Expected: the request routes instead of erroring.
Batch multiple IDs in one call to stay under rate limits, and keep render and image-fill URLs separate since they come from different hosts. Expected: this specific failure stops.
Details
When rendering images from the Figma API, do not trust the HTTP status alone. The download URLs in the response are temporary signed links, so download immediately instead of storing them for later.
When to use
You hit exactly this: Image renders return 200 with null for bad node IDs, and URLs expire in Image.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Image.
Evidence
Web (api-gateway-skill figma reference): documents two image-render gotchas that break naive automation: a nonexistent node ID in a render request is not an error, it returns 200 with a null value per ID, and the returned render URLs are temporary links that expire. Node IDs also need the colon form. Resolved: When rendering images from the Figma API, do not trust the HTTP status alone. Requesting a nonexistent node ID returns 200 with {"err": null, "images": {"99999:99999": null}}; check every value for null and treat nulls as bad IDs, not as successful renders. The download URLs in the response are temporary signed links, so download immediately instead of storing them for later. Use the colon form of node IDs (1:2) even though Figma URLs show the dash form (1-2). Batch multiple IDs in one call to stay under rate limits, and keep render and image-fill URLs separate since they come from different hosts.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_6SbzpQJW8dD8lLWsVLNggA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Image renders return 200 with null for bad node IDs, and URLs expire <span>— Vectle</span></a>