Connect Studio to Code

Using the Studio CLI and API

This documentation provides a detailed guide on how to use the Studio CLI and API for managing design tokens efficiently.

Accessing the SDK and CLI Documentation

Navigate to Studio:
- Open the Studio application.
- Go to your organization dashboard.
- Click the SDK and CLI button.
Review the SDK Documentation:
- This page contains the Studio Software Development Kit (SDK) and CLI instructions.
- It might seem overwhelming, but the focus is on pulling your tokens into your local file system via the CLI.
Creating an API Key
- Generate a Key:
  - Go to Personal Settings in Studio.
    Select API Keys (below "Edit Profile").
    Create a new API key (e.g., "Test Key").
- Copy and Store the Key:
  - Copy the key string and store it securely (e.g., in a password manager or vault).
    You won’t be able to view the key again after closing the window.

Using the API Key with GraphQL

The API operates on a GraphQL interface. You can use tools like Postman, Curl, or the Apollo Sandbox to interact with it.

Access the Apollo Sandbox:
- Open the GraphQL endpoint https://graphql.app.tokens.studio/graphql

Configuring the Authorization Header:

In Apollo Sandbox:
- Navigate to Settings > Connection Settings.

Click on Edit on the Connection settings. A modal will open.

In the Shared headers section, select "Authorization header" in the header key input. In the value input: Bearer <API_KEY> (replace <API_KEY> with your API key). Click Save.

View the available queries:

The query section will show the available queries as can be seen in the SDK-CLI documentation > Query page.

Run a Query:

Use the query editor in Apollo Sandbox to explore data (e.g., list all projects).

Example query - List of all projects in an Organization:

Click on "projects(...): PaginatedProjects!". The details will be filled in the Operation and Variables section.

Add "data: [Project!]!. This step is done because the Projects list is a paginated response.

Add "name" to get the name of the project and "oragnizationId" to specify the organisation.

A query would be generated in the Operations panel.

query Projects($organization: String!) {
  projects(organization: $organization) {
    data {
      organizationId
      name
    }
  }
}

In the "Variables" section, we need to add the organisation id. To get the organisation ID, Navigate to your organization in Studio. Copy the Organization ID from the URL (after /org/).

Return to the Apollo Sandbox, enter the organisation id in the "Variables section".

{
  "organization": "<org-ID>"
}

Run the query, the list of projects with the project name and the organisation id will be displayed in the right panel.

Using Postman to Call the API

Set Up a Request:
- Create a new POST request in Postman.
- Use the same endpoint as Apollo Sandbox.

Add Authorization:

In the Authorization tab, select Bearer Token.
Paste your API key into the token field.

Check the Headers:

The headers will show a predefined Authorisation.

Define the Body:

Go to the Body tab. Select the "raw" option. In the input enter the "operationName" and "variables" as we have defined in the Apollo Sandbox.

Use the "query" in the "Operation" section of Apollo Sandbox and convert it into a single-line string. You can use this tool to convert the query from multi-line to single-line.

The single line query will look like this:

query Projects($organization: String!) {\n  projects(organization: $organization) {\n    data {\n      organizationId\n      name\n    }\n  }\n}

Provide necessary variables (e.g., organization ID) in the payload. The final query will look something like this:

{
    "operationName": "Projects",
    "variables": {
        "organization": "<Org-ID>"
    },
    "query": "query Projects($organization: String!) {\n  projects(organization: $organization) {\n    data {\n      organizationId\n      name\n    }\n  }\n}"
}

Send the Request:

Execute the request by clicking on "Send" to receive JSON responses similar to the Apollo Sandbox.

Using the Token Studio CLI

Install the CLI:
- Open the project that you want to connect Studio with.
- Run npm install @tokens-studio/sdk.
- If you don’t have a package.json, initialize it first with npm init.
- Ensure that the node.js version installed is v.22 or above.
```
npm install @tokens-studio/sdk
```

Run the CLI:

Use the --help flag to view available commands:

npx tokensstudio --help

This will list all the available options

Tokens Studio CLI  2.0.2

Usage:
$ tokensstudio 
   
Commands: 
pull
setup

For more info, run any command with the `--help` flag:
$ tokensstudio --help
$ tokensstudio pull --help
$ tokensstudio setup --help 

Options:
--help       [boolean] Shows an overview of CLI usage
--version    [boolean] Prints NPM version of the CLI

Set Up the CLI:

Run the setup command:

npx tokensstudio setup

Enter your API key when prompted. You can skip this step by Automating the CLI.

Tokens Studio CLI  2.0.2

You did not pass an API key in the environment variables, but you can paste one here.
      You can create an API key in Studio user settings by navigating to a project dashboard 
      and clicking the bottom left menu -> API keys.

               API key:

Select the desired organization and project.

✔  Done!
         ■ Fetched organizations
         ■ Fetched projects

Select your organisation
Hyma

Select your project
Tokens Zen Garden

The selected settings will be saved in the .tokensstudio.json config file.

{
"version": "2",
"org": "7xxxxxx1-3xx5-4xxx-xxx6-xxxx4axxxxf2",
"project": "xxxxfa7d-xxxx-4xxx-xxx2-xxxx0126xxxx",
"branch": "main",
"release": "",
"output": "tokens"
}

Pull Tokens:

Specify the folder to pull tokens into (relative to the config file). This can be done in the .tokensstudio.json config file as output.
Use the pull command:

npx tokensstudio pull

This will pull all the tokens in your project into the output specified in your config (.tokensstudio.json) file.

      ✔  Done!
         ■ Fetched tokensets

      ✔  Success Found 18 sets with 938 tokens in total.
         ◼   global.json
         ◼   semantic.json
         ◼   comp/button.json
         ◼   comp/list-item.json
         ◼   comp/menu-item.json
         ◼   comp/toggle.json
         ◼   pattern/menu-bar.json
         ◼   pattern/feature.json
         ◼   pattern/card-user.json
         ◼   pattern/card-pricing.json
         ◼   sections/nav.json
         ◼   sections/hero.json
         ◼   sections/features.json
         ◼   sections/team.json
         ◼   sections/pricing.json
         ◼   sections/footer.json
         ◼   theme/light.json
         ◼   theme/dark.json

Automate the CLI:
- Pass the API key as an environment variable for automation. This will ensure that the API key is not prompted for everytime.
```
TOKENSSTUDIO_APIKEY=<API_KEY> npx tokensstudio pull
```

Key Features of the CLI

Current Features:
- Pull token sets into local files.
- Simplify organization and project selection.
Planned Features:
- Watch Mode: Automatically sync changes from Studio to local files.
- Release Artifacts: Pull releases directly instead of token sets.

Best Practices

Secure API Key Storage:
- Use a password manager or secure vault.
- Avoid storing keys in plain text.
Automation:
- Use environment variables to prevent manual prompts in CI pipelines.
Explore API Schema:
- Use Apollo Sandbox for schema introspection before creating complex queries.

This documentation provides an overview of using Studio’s API and CLI effectively. For further assistance, refer to the official SDK and CLI documentation page.

PreviousUsing Companion by Tokens Studio NextFeatures

Last updated 2 months ago