GET /v1/files/{file_key}
Returns the document identified by file_key as a JSON object. The file key can be parsed from any Figma file url: https://www.figma.com/file/{file_key}/{title}.
The document property contains a node of type DOCUMENT.
The components property contains a mapping from node IDs to component metadata. This is to help you determine which components each instance comes from.
Servers
- https://api.figma.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
file_key |
String | Yes |
File to export JSON from. This can be a file key or branch key. Use |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
branch_data |
Boolean | No |
Returns branch metadata for the requested file. If the file is a branch, the main file's key will be included in the returned response. If the file has branches, their metadata will be included in the returned response. Default: false. Default value: false |
version |
String | No |
A specific version ID to get. Omitting this will get the current version of the file. |
depth |
Number | No |
Positive integer representing how deep into the document tree to traverse. For example, setting this to 1 returns only Pages, setting it to 2 returns Pages and all top level objects on each page. Not setting this parameter returns all nodes. |
ids |
String | No |
Comma separated list of nodes that you care about in the document. If specified, only a subset of the document will be returned corresponding to the nodes listed, their children, and everything between the root node and the listed nodes. Note: There may be other nodes included in the returned JSON that are outside the ancestor chains of the desired nodes. The response may also include dependencies of anything in the nodes' subtrees. For example, if a node subtree contains an instance of a local component that lives elsewhere in that file, that component and its ancestor chain will also be included. For historical reasons, top-level canvas nodes are always returned, regardless of whether they are listed in the |
plugin_data |
String | No |
A comma separated list of plugin IDs and/or the string "shared". Any data present in the document written by those plugins will be included in the result in the |
geometry |
String | No |
Set to "paths" to export vector data. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.