Have you ever wanted to extend Zeplin’s capabilities to better suit your team’s workflow?
Some example workflows you can build with the SDK include downloading all of your project assets in bulk and downloading a backup of all the screens in your entire workspace. Check out our Zeplin Community GitHub Repo for some more inspiration with the SDK, including the code sample shown below.
1.Generating your Personal Access Token
2.Starting your Node app
3.Install the SDK
4.Authenticate the SDK with your Personal Access Token
You can also find a full walkthrough of these steps in this video:
Generating your Personal Access Token
The first thing you’ll need is a Personal Access Token. To get this, log in to Zeplin’s Webapp, select your avatar in the upper-right corner, and select your email address to go to your profile:
Select the “Developer” Tab and then click “Create new token”
A new screen will pop-up where you can enter a name for your token.
For privacy, the Zeplin API will obfuscate email addresses of users in any endpoint response by default, but if this is required for your workflow then you can check “Enable admin access”. Then click “Create”.
Copy your Personal Access Token to your clipboard and store it somewhere safe because it will disappear once you navigate away from that screen.
Start your Node app
In your terminal, create a new directory for our Node app to live in and enter the directory. We’ll call ours “zeplin-sdk-demo.”
Initiate your Node app with “npm init” and answer the setup questions. If you want to use all the default settings, you can use “npm init -y”
Install the SDK
From here, we’ll want to use “import” syntax, so we can update package.json to indicate that the type of app you have is a “module”
Authenticate the SDK with your Personal Access Token
The entry point of the app is index.js, so we can open that file in your editor now. This is where you’ll import the Zeplin SDK and authorize it with our Personal Access Token.
Note: If you’re going to be sharing this app with anyone, it’s best practice to use a library like dotenv to safely store your Personal Access token into a .env file that is only available to you locally and Git ignored.
Let’s try it out! We can make a call to the getCurrentUser endpoint to return some information about yourself:
Now we can run this code in your terminal with:
Which will log something like:
If you have any questions or want to share what you're building, come join the developer community on our Discord server!