Create a message for Figma about variable overrides

[airikej]

extended variables

[airikej]

Currently, the endpoint GET /v1/files/:file_key/variables/local provides access to variable definitions, including valuesByMode and aliasing. However, it does not expose variable overrides or resolved values as they are applied within document nodes.

When developing a Figma plugin, it is possible to access both:

• Primitive variable values
• Variable overrides at the node level

This makes it feasible to fully understand how design tokens are applied in context. However, this same level of access is not available via the REST API, which creates a gap for external tooling.

Use Case

Designers often need the flexibility to define their own colors or values on top of an existing design system—for example, creating themes or brand-specific variations. These overrides are essential for real-world workflows where a base system is extended rather than replaced.

From a development perspective, it would be extremely useful to fetch these overrides directly via the API. This would allow developers to retrieve the exact values used in a design (including themed overrides) with a simple request, enabling smoother integration between design and implementation.

Current Limitation

While node data includes boundVariables, it does not provide:

• The resolved variable values per node
• Any indication of overrides versus inherited/default values

Feature Request

It would be extremely valuable if the REST API could expose variable overrides in one of the following ways:

• Node-level resolved variables
• A field such as resolvedVariables or computedVariables per node
• Explicit override metadata
• A way to distinguish between default values and overrides
• Optional expansion parameter
  For example: ?include=variableOverrides or ?resolveVariables=true

This would bring the REST API closer to feature parity with the plugin API and unlock more robust integrations.

Impact

Providing this functionality would:

• Enable more accurate design-to-code pipelines
• Reduce the need for plugin-based workarounds
• Support teams building tooling outside of Figma
• Improve consistency between plugin and REST API capabilities

[airikej]

@kaiajallai @karolin-kivisikk panin siis selle kirja kokku arendaja vaatest, vt eelmine kommentaar