Skip to main content

Hello,


I know I can follow these steps to show the file version history sidebar:


View a file’s version history – Figma Learn - Help Center


And I know I can share a version using these steps:


View a file’s version history – Figma Learn - Help Center


However, when I follow these steps, there’s no Copy Link option for the Current version. At one level, that makes sense, since in the browser, the address bar contains a link to the current version.


However, what I’m looking for is the current version such that it includes the current version-id.


For example -


https://www.figma.com/design/:fileId/FileDescrition?version-id=5662857941&node-id=1-3304&node-type=canvas&t=:anotherId


By copying the address bar value, the version-id is not included. And if the design changes, then the URL that was copied from the browser address bar no longer reflects what I was looking at the time I earlier copied it. The URL without the version-id is “evergreen”, always showing the latest. I’m looking for the current latest version, at a given point in time. How would I get that?


Thank you!

You can get the current version ID using the REST API (for example, the GET file versions endpoint). You can also use the saveVersionHistoryAsync method of the Plugin API to save a new version and get its ID.

Thank you for your reply! I’ve tried the GET file versions endpoint, and I do set a list of versions in the response.


By cross referencing the URLs “version” for the last non-“current” version in the file’s view history in the sidebar, I can see a recent version in the GET file versions response.

But one thing that is surprising – I see multiple entries after the matching non-current version in the GET file version response, while in the view history UI in the sidebar, I see just one “current version”. So, I’m unclear on what the ultimately “latest” version is. I guess it is always the last response from the GET file version endpoint, so if I call this from a plugin and just take the last version in the response, I imagine that should work.


The saveVersionHistoryAsync API sounds pretty great, except some users are viewers only (e.g. developers) who do not have permission to save new revisions I think, so I imagine that API call would fail.

Reply


Terms & ConditionsCookie settings