Figma Api

REST API at api.figma.com/v1. Resources: files, nodes, components, component_sets, styles, variables, comments, versions, projects, webhooks. GET /v1/files/{fileKey} returns the full file document tree (JSON, potentially large for big files). GET /v1/files/{fileKey}/nodes?ids={nodeIds} returns specific nodes by ID. GET /v1/files/{fileKey}/components returns all published components. GET /v1/files/{fileKey}/variables/local returns all variables (design tokens) in the file. POST /v1/files/{fileKey}/comments adds a comment. GET /v1/files/{fileKey}/images exports nodes as PNG/JPG/SVG/PDF. Pagination via cursor for large result sets.

Figma's REST API gives programmatic access to design file structure — every frame, component, text node, and style in a Figma file can be read via the API. Key agent use cases: extracting design tokens (variables) for use in code generation pipelines, reading component properties for documentation automation, posting automated review comments on design files, and exporting specific assets (icons, images) programmatically. Webhooks notify agents of file changes. OAuth2 for user-context access; personal access tokens for service/automation access. Well-designed API with clean JSON responses. Confidence is docs-derived.

OAuth2 for user-delegated access (Authorization Code flow — browser redirect required). Personal Access Tokens for programmatic/service access: generated in Figma Account Settings → Personal access tokens. Passed as X-Figma-Token: {token} header (or Authorization: Bearer for OAuth2). Tokens have full account access; no per-scope restriction. HTTPS enforced. Webhook verification via HMAC-SHA256 signature on payload. Token rotation via Figma account settings.

figma.com/developers/api provides the full API reference with all endpoints, response schemas, and type definitions. Webhook configuration guide available. OAuth2 flow documentation included. Getting started requires a Figma account (free tier sufficient for API access). Personal access tokens easy to generate. TypeScript types available (community-maintained figma-js package). Plugin API (different from REST API) for in-editor plugins. Community support via Figma Community Forum and dedicated API support for paid plans.

Standard HTTP status codes with JSON error bodies (status, err message). 403 for missing file access or invalid token. 404 for missing file/node. Large files: GET /v1/files may time out or return partial results — use node-specific GET /v1/files/{key}/nodes for targeted access. Image export is async: GET /v1/files/{key}/images returns URLs; rendered images may take seconds to be available. Rate limit: 300 requests per minute per file per token. Figma platform uptime at status.figma.com.