Figma REST API
✓ Official Vendor SpecProductivityCollaborationapiKey,oauth238 EndpointsREST
For Agents
Read Figma files and projects, post comments, manage components and variables, render images, and subscribe to webhooks across 38 endpoints, with PAT or OAuth2 auth.
Use for: Get the structure of a specific Figma file, Render a node as a PNG image, Post a comment on a frame in a file, List all projects in a Figma team
Not supported: Does not handle real-time multiplayer cursors, plugin runtime, or local file editing — use for reading and writing Figma file metadata, comments, and rendered assets only.
The Figma REST API provides programmatic read and write access to Figma files, projects, comments, components, styles, variables, webhooks, dev resources, activity logs, and user information. It exposes 38 endpoints, including specialised operations like rendering images from a file and retrieving image fills. Authentication supports both Personal Access Tokens via the X-Figma-Token header and OAuth2 for delegated app integrations.
Install Jentic One Beta
Connect the Figma REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Figma REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Figma REST API.
Retrieve file structure and individual nodes from a Figma design
Render PNG, JPG, SVG, and PDF images from selected nodes
Post and delete comments on a file with reactions
List components, component sets, and styles published in a team
Read and update local variables and variable collections inside a file
Subscribe to webhooks for file updates, comments, and library publications
Use Cases
Patterns agents use Figma REST API for, with concrete tasks.
★ Design-to-Code Asset Export
Export design assets directly from Figma files into a build pipeline. The API exposes GET /v1/images/{key} to render selected nodes as PNG, JPG, SVG, or PDF in one call, plus GET /v1/files/{key}/images for image fills already embedded in the file. This replaces manual export-and-upload steps and scales to dozens of assets per build.
GET /v1/images/{key}?ids=node-id&format=png&scale=2 and return the rendered image URL
Design Review Comment Automation
Post structured review comments on Figma frames from CI checks or accessibility scanners. POST /v1/files/{key}/comments accepts a node-anchored payload, and DELETE removes them when issues are resolved. Useful for design-system enforcement workflows where automated checks should leave actionable feedback in context.
POST /v1/files/{key}/comments with the message text and the target node_id from a failing accessibility check
Component Library Sync
Mirror Figma component metadata into a developer documentation site or design tokens pipeline. The API surfaces /v1/files/{key}/components and team-level component endpoints so an agent can pull canonical names, descriptions, and keys for downstream syncing. Handles libraries with hundreds of components without manual listing.
GET the team components endpoint, filter by library_key, and write a JSON mapping of component name to key
AI Agent Design Inspection via Jentic
Through Jentic, an agent can answer questions like which frames lack alt text or how many components a team published last week. Jentic exposes Figma's file, comment, and component operations as discoverable tools, letting a Claude or GPT agent inspect designs and post feedback without writing custom plugins.
Search Jentic for 'get figma file', call GET /v1/files/{key}, and return frames missing accessibility annotations
Key Endpoints
38 endpoints — the figma rest api provides programmatic read and write access to figma files, projects, comments, components, styles, variables, webhooks, dev resources, activity logs, and user information.
METHOD
PATH
DESCRIPTION
GET
/v1/files/{key}
Get a file
GET
/v1/files/{key}/nodes
Get specific nodes
GET
/v1/images/{key}
Render rendered images
POST
/v1/files/{key}/comments
Post a comment
GET
/v1/teams/{team_id}/projects
Get team projects
GET
/v1/projects/{project_id}/files
Get project files
GET
/v1/files/{key}
Get a file
GET
/v1/files/{key}/nodes
Get specific nodes
GET
/v1/images/{key}
Render rendered images
POST
/v1/files/{key}/comments
Post a comment
GET
/v1/teams/{team_id}/projects
Get team projects
GET
/v1/projects/{project_id}/files
Get project files
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Figma Personal Access Tokens and OAuth2 credentials are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access — the raw X-Figma-Token header value never enters the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'render a figma node as png') and Jentic returns the matching GET /v1/images/{key} operation with its schema, so the agent calls it without reading the Figma developer docs.
Time to first call
Direct Figma integration: 2-3 days for OAuth setup, scope handling, and rate-limit retries. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Figma REST API through Jentic.
What authentication does the Figma REST API use?
Figma supports two methods: a Personal Access Token sent as X-Figma-Token, and OAuth2 for third-party app integrations. Through Jentic both are stored encrypted in MAXsystem and never enter agent context.
Can I render a Figma node as an image through the API?
Yes. GET /v1/images/{key} accepts node IDs and a format parameter (png, jpg, svg, pdf) and returns rendered image URLs hosted by Figma's CDN.
What are the rate limits for the Figma REST API?
Figma applies different limits per endpoint; image rendering and file fetching have lower per-minute caps than metadata reads. Check developers.figma.com for current values, which may change with plan tier.
How do I post a comment on a file through Jentic?
Search Jentic for 'post figma comment', load the POST /v1/files/{key}/comments schema, and execute with the message and target node_id. Run pip install jentic to start.
Does the Figma API support webhooks?
Yes. The Webhooks resource lets you subscribe to events such as FILE_UPDATE, FILE_COMMENT, and LIBRARY_PUBLISH so agents can react to design changes without polling.
Can I read and update Figma variables through the API?
Yes. The Variables endpoints expose local variables and variable collections inside a file, supporting design-token sync workflows. Updating variables requires the variables:write OAuth scope.
GET STARTED