Token API
Tokens are published as read-only, versioned, machine-readable JSON. These endpoints are a publishing channel, not a build dependency: applications never download anything from here while building.
Endpoints
GET /design/tokens.json | All tokens in one file (latest) |
GET /design/manifest.json | Version and sha256 list (latest) |
GET /design/v1/tokens.json | All tokens, API version 1 |
GET /design/v1/manifest.json | Manifest, API version 1 |
GET /design/v1/typography.json | Typography only |
GET /design/v1/motion.json | Motion only |
Version
The v1 in the path is the version of the JSON structure; an incompatible change opens v2. The content version is the version field in the manifest and is derived from the sources: it changes only when a source changes.
Current content version: aac9e9481fe2
Verification
The manifest carries the sha256 of every published file. Compare it with your copy to see whether your copy is current.