Zeplin
Zeplin is a design-to-development handoff platform that bridges the gap between designers and developers by providing a structured workspace for accessing design specs, assets, style guides, components, and annotations. The Zeplin REST API enables programmatic access to all resources within Zeplin including projects, screens, components, layers, assets, and notes exported from Figma, Sketch, and Adobe XD. Developers can build custom integrations using read and write operations on design data, receive real-time updates via webhooks, and automate design-to-code workflows. The API uses OAuth 2.0 with PKCE support and personal access tokens for authentication, with an official JavaScript SDK and OpenAPI specification available.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Zeplin the way a machine reads it — 44 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zeplin scores 44.0/100 (developing), with a separate agent-readiness read of 40/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Zeplin's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zeplin/"
title="Zeplin on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zeplin.svg"
alt="Zeplin Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/zeplin/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zeplin/"
title="Zeplin on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zeplin/card.svg"
alt="Zeplin Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Zeplin
Each block below is one kind of artifact we hold for Zeplin. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Zeplin Authorization API
The Authorization API from Zeplin — 2 operation(s) for authorization.
Zeplin Colors API
The Colors API from Zeplin — 4 operation(s) for colors.
Zeplin Components API
The Components API from Zeplin — 10 operation(s) for components.
Zeplin Connected Components API
The Connected Components API from Zeplin — 2 operation(s) for connected components.
Zeplin Design Tokens API
The Design Tokens API from Zeplin — 2 operation(s) for design tokens.
Zeplin Flows API
The Flows API from Zeplin — 7 operation(s) for flows.
Zeplin Notifications API
The Notifications API from Zeplin — 2 operation(s) for notifications.
Zeplin Organizations API
The Organizations API from Zeplin — 11 operation(s) for organizations.
Zeplin Projects API
The Projects API from Zeplin — 5 operation(s) for projects.
Zeplin Screens API
The Screens API from Zeplin — 17 operation(s) for screens.
Zeplin Spacing API
The Spacing API from Zeplin — 6 operation(s) for spacing.
Zeplin Styleguides API
The Styleguides API from Zeplin — 6 operation(s) for styleguides.
Zeplin TextStyles API
The TextStyles API from Zeplin — 4 operation(s) for textstyles.
Zeplin Users API
The Users API from Zeplin — 3 operation(s) for users.
Zeplin Variable Collections API
The Variable Collections API from Zeplin — 2 operation(s) for variable collections.
Zeplin Webhooks API
The Webhooks API from Zeplin — 8 operation(s) for webhooks.
Scroll within the panel for all 16 ·
Open Collections 17
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONZeplin Authorization API
OPEN COLLECTIONZeplin Authorization Colors API
OPEN COLLECTIONZeplin Authorization Components API
OPEN COLLECTIONZeplin Authorization Connected Components API
OPEN COLLECTIONZeplin Authorization Design Tokens API
OPEN COLLECTIONZeplin Authorization Flows API
OPEN COLLECTIONZeplin Authorization Notifications API
OPEN COLLECTIONZeplin Authorization Organizations API
OPEN COLLECTIONZeplin Authorization Projects API
OPEN COLLECTIONZeplin Authorization Screens API
OPEN COLLECTIONZeplin Authorization Spacing API
OPEN COLLECTIONZeplin Authorization Styleguides API
OPEN COLLECTIONZeplin Authorization TextStyles API
OPEN COLLECTIONZeplin Authorization Users API
OPEN COLLECTIONZeplin Authorization Variable Collections API
OPEN COLLECTIONZeplin Authorization Webhooks API
OPEN COLLECTIONScroll within the panel for all 17 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Zeplin GraphQL Schema
This document describes a conceptual GraphQL schema for the Zeplin design handoff and collaboration platform. Zeplin bridges designers and developers by providing structured acc...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Zeplin Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Zeplin Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Zeplin Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Zeplin Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Zeplin API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Zeplin API Schemas
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Zeplin — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zeplin · machine-readable index on apis.io
This is an independent, third-party profile of Zeplin, 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.