A designer’s guide to the Figma API

Part 5 of 7 — Processing the response.

You can find the code for this tutorial here:

In Part 4, we managed to get our server to talk to a Figma endpoint and dump the results. Now we need to process the results and make a query to a different Figma endpoint to get the images we need.

Filtering out all the crap

Going back to our Figma file quickly, we just have 4 frames, each of which has a card symbol and a button group:

All we want to get for the purpose of this tutorial is those 4 frames. So how do we filter out all the other crap?

Before we can do that we need to look a little bit closer at what the JSON structure looks like. If we boil it down it looks something like this:

- document
  |- children
     |- canvas
        |- children
           |- frame
           |   |- children
           |       |- component
           |       |- group
           |- frame
           |    |- children
           |       |- component
           |       |- group
           |- frame
           |    |- children
           |       |- component
           |       |- group
           |- frame
           |    |- children
           |       |- component
           |       |- group

Inside the document object there is an array called children that contains all the canvases (our document only has once canvas). The canvas object also contains an array called children that contains all the frames in the document. These frames are what we need.

Okay, now we have a clearer picture of the structure we can change figmaFileFetch() inside server.js to look like this:

This code is quite confusing at first. Lets break it down:

• //1 Our big chunk of JSON is stored in figmaFileStruct much like before, but now instead of returning that, we create a new variable called figmaFrames and make it equal to something. By declaring a variable on the left side of an = like this, we are assigning its value to whatever is on the right side of the =. In this case we are making it equal to the children array inside of the document object that we described in the diagram above.

• // 2 Before this whole equation can resolve, we are using the .filter() method to find the parts of the children array we want. .filter() is a built in array method that literally filters through each item of an array based on the arguments we give it. It’s like saying “Hey, go look through that list and make a new list with every item that has the letter p in it!” In our code we filtering any items that have the type of CANVAS. That should give us all the canvases in our doc but we know we only have one. So we use the [0] on the end of filter to access the first child of the array. And .children to access the children array inside our frame object. In terms of the tree we used before:

• //3 Once again, we use .filter(). Remember that filter makes a new array with the results, and doesn’t change the original one. So now we are filtering the array we just created on the line above. This time we want all the items in this array with a type of FRAME. In our case there are 4 items that match that description — leaving us with an array of 4 frame objects:

• //4 Next we use the .map() method. This is another built in array method and it allows us to iterate through an array. This is like saying “Hey, for every item in that list that contains the letter p, make a new list and replace it with the letter d”. We are using this step to structure the array we are going to return. Instead of the 4 whole frame objects, we only need to know the frame’s name and id. So for every frame object, we make a new simpler object that looks like this { name: frame.name, id: frame.id } and store them in our array. This is the value that will be passed into our figmaFrames variable and that we return.

If you hit refresh on http://localhost:3001/ you should see something like this:

Getting images from Figma

In Part 1 we discussed that Figma has several endpoints and so far we have only been interacting with one of them. We give it our API Key and a file id and it returns JSON describing the file. The endpoint we need to use next takes our API key, the file id AND the ids of the elements we want to display. It then returns the urls for the images of our frames.

We have everything we need to ask Figma for the image urls, we just need to write some more code:

Lets run through this:

1. Firstly, we need to have a list of all the ids we want. The Figma endpoint needs these ids to figure out which elements to show. So we create a variable called ids and use .map() to pull out all the ids in our figmaFrames array. Importantly we use .join() to take all the ids and add them together in a comma separated string ie: 123,132,321,231. The ids will be included in our URL so we need them as a string.
2. You’ll recognise this fetch() call from earlier — it’s very similar to the one we use for the file endpoint. Just like before, it’s an async call meaning we expect the response to take a while. This time we are constructing a different url: - Instead of ‘https://api.figma.com/v1/files/' we need to use ‘https://api.figma.com/v1/images/' as the base of our url. Just like previously we append our fileId. - The next part of the url, ‘?scale=2&ids=’ is a bit confusing, but it includes the scale of the images we want to return. I have hardcoded 2x in there, but you could do your own thing if you want. - Lastly, we add our comma separated list of ids. The rest is the same as before. We use our API Key to construct a header to authenticate this request against Figma’s servers. We also add a catch() here to print any errors to the console (we probably should have done this earlier too)
3. Here we are parsing the result into JSON, so we can easily work with the data. We are doing this asynchronously because we don’t know for certain that the result has resolved yet.
4. This is a bit of a strange line but the response we get from the Figma endpoint has a few other things attached to it. We are only interested in the image object inside of it. Here we make our variable equal to one of its own children objects, essentially throwing away the extra info.
5. At this point in time our figmaImages array contains objects with ids and urls. We don’t need those ids anymore, so before we return the data, we clean it up so that each object has a name: and url: instead. The frame names aren’t in our figmaImages so we are rather going to update the figmaFrames array we have from above. We simply need to swap out the ids with the urls that we have in figmaImages using .map(). Now our objects look like this: {“name”:”Left Aligned”, ”url”:”https://reallylongurl"}.

And that’s sort of it. Every time a client goes to that path it will get a response from our server. That response will now be an array with names and urls.

Technically we could end this tutorial here, as we achieved what we set out to do. But it feels like a bit of cop-out to end things here. In Part 6 we are going to hook up a front-end client to talk to our server and display the image results we get back.

If you want more super long, boring content like this make sure to follow me here. If you want some short-form boring content, follow me on twitter.