Zeroheight API
The zeroheight REST API automates design system workflows: read styleguides, their categories, pages and page content (Markdown available via ?format=markdown), read published styleguide versions and design token sets, and write page status tags. Authentication is a paired Client ID and Access Token sent as the X-API-CLIENT and X-API-KEY headers. Rate limited to 30 requests per 30 seconds per key. API access is an Enterprise-plan feature.
Zeroheight API is one of 2 APIs that Zeroheight publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Design System, Design Tokens, Documentation, REST, and Style Guides. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.
This API exposes 9 operations across 8 paths, organized into 3 resource areas, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version v2.
Requests are made against a single base URL, https://zeroheight.com/open_api/v2.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Zeroheight API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as X-API-CLIENT (apiClient).
An API key is passed in the header as X-API-KEY (apiKey).
By default, every request must be authenticated.
apiClient— The Client ID generated in the Developers section of zeroheight organization or workspace settings. Client IDs are prefixed zhci.apiKey— The Access Token generated alongside the Client ID. Shown once only, treated like a password. Access tokens are prefixed zhat.
Paths & Operations 9
Across 8 paths, the API surfaces 9 operations — 8 GET, 1 PATCH. They span 3 resource areas: Styleguides, Pages, Tokens. Each is listed below with its method, path, parameters, and response codes.
Design systems documented in zeroheight. A styleguide is the top-level container for pages, categories and versions.
Individual documentation pages inside a styleguide, including their content and status tag.
Design token sets managed in the zeroheight token manager.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ErrorEnvelope (3 properties), SuccessEnvelope (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Zeroheight 1
Other APIs Zeroheight publishes across the network.
This is an independent, third-party profile of Zeroheight API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.