API documentation is available at developers.zeroheight.com

Before you get started

• Authentication tokens belong to your team, making it easier to monitor token activity, manage creation, and revoke tokens as needed.
• While the Client ID can be shared, the Access Token should be treated with the same care as a password. If both your Client ID and Access Token are exposed, they could be exploited to access or modify your content on zeroheight. If you suspect a leak, revoke the token immediately.
• You can create and manage as many authentication tokens as needed, as often as necessary.

Token creation

To create a new authentication token, navigate to the Developers section in your organization's or workspace's settings. You’ll need to provide the following details:

• Token name: A descriptive name to help you easily identify the token.
• Use case: Choose pre-defined scopes tailored to your intended purpose (see the "Token use cases" section below for details).
• Granular token scopes: Pick specific CLI scopes for precise control over access levels and use case (available to Enterprise customers only).

Once created, take note of your Client ID and Access Token:

• The Access Token will only be displayed once, so make sure to save it securely.
• The Client ID will remain accessible in your organization’s or workspace’s settings.

Token use cases

You can select a use case to pre-define scopes for your token. Learn more about the respective features of each use case:

• Measure Adoption: Authenticate with @zeroheight/adoption-cli to monitor package versions, track component usage, and more. Learn more about adoption features.
• Zapier: Authenticate with Zapier to build customized automation workflows. Learn more about automation with Zapier.
• Style Dictionary Exports: Authenticate to access private token export URLs. Learn more about token exports.