Specify's mission is to empower organizations to manage their branding at scale.

Every design decisions can be taken in one tool and needed by another. Organizations need their tools to be able to "talk to each other" so that these decisions can navigate freely. Also, to be successful your design system must be fully networked. The perfect way of doing this is by using an API.

Specify is composed of:

  • a database—to store your design data

  • a design API—to get your design data

  • a list of open source parsers—to transform your design data

A design API, Kesako?

Specify provides the first Design API allowing you to send your design tokens and assets across your design system tools. Specify is built with this idea: configure once, synchronize anytime.

Extract design data from sources and...

Let's say your design tokens are defined in a design tool like Figma. These design decisions are meant to serve the final product and your end users. They need to be used—consistently—by developers. To make a long story short, these design decisions have to be extracted by Specify from the place they've been defined: their source.

...Distribute them to destinations

Extracting your design decisions inside Specify is only building the first half of the bridge closing the gap between designers and developers. Why? Because developers need to get design decisions tailored for their needs. This is why Specify helps you distribute your design decisions to the right tool, in the right format and at the right time.

How does the Specify API work?

You can get design tokens either by using:

  • Our REST API

  • The Specify CLI

  • A Destination application—GitHub is the only destination available at the time being

These different ways of extraction help you get your design tokens with flexibility. Whatever way you choose you'll be able to transform your design data exactly the way you want.

There is not "one way of extracting design tokens to rule them all". Use the one that suits best your workflow.

👉 See how to use the Specify API on our dedicated documentation.

Did this answer your question?