The API Report CardAPI Index
Zeplin

Zeplin API

Design Handoff & Collaboration · zeplin.io

Zeplin ships a public REST API with an open-source OpenAPI spec and an official JavaScript SDK. Personal access tokens are self-serve from the profile Developer tab; public OAuth apps need manual registration. Webhooks are first-class, and the documented limit is 200 requests/min per user.

Last verified: July 2026Software & Data Tools
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODFirst-class public REST API with an open-source OpenAPI spec on GitHub and a webhook system.
AccessGOODPersonal access tokens are self-serve and API access is bundled with paid plans; public OAuth apps require contacting Zeplin.
CoverageGOODReads span projects, styleguides, screens, components, layers, and assets; writes cover notes, components, and styleguide objects.
AuthGOODPersonal Access Tokens or full OAuth2 apps, both created from the Developer tab in the user profile.
Docs & DXGOODdocs.zeplin.dev plus an official JS SDK for Node and browsers; webhook retry and auto-deactivation rules are spelled out.
StabilityGOOD
Supergood: Zeplin shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Zeplin scores A on the API Report Card. Zeplin ships a public REST API with an open-source OpenAPI spec and an official JavaScript SDK. Personal access tokens are self-serve from the profile Developer tab; public OAuth apps need manual registration. Webhooks are first-class, and the documented limit is 200 requests/min per user.

Tried to integrate with Zeplin?
SOURCES
Rate limit of 200 req/min per user is restrictive for large enterprise automations (e.g., bulk asset sync across thousands of screens) docs.zeplin.dev
Some resources are read-only, customers cannot fully CRUD all object types (e.g., create projects/screens programmatically), forcing manual setup in the UI support.zeplin.io
Webhook auto-deactivation after 10 failures/hour can silently disable production integrations; teams have to monitor email for outage notifications docs.zeplin.dev
Customers report having to invest in building Figma-API + Zeplin-API integrations themselves; Zeplin does not offer a managed automation layer g2.com
No GraphQL endpoint; pagination is offset/limit on REST which is awkward for very large projects docs.zeplin.dev
OAuth app approval is manual, third-party app developers must contact Zeplin to register a public app, slowing marketplace growth docs.zeplin.dev
Figma Dev Mode largely overlaps Zeplin's core value; many teams have stopped paying for Zeplin once they fully adopted Figma trustradius.com
No offline mode, users complain about loading screens and unusable handoff when connectivity is poor g2.com
Seat-based pricing on paid plans restricts reviewer/contributor access; the free plan allows unlimited reviewers but paid plans don't, which large teams find unfair g2.com
Cost adds up at scale: paid Advanced tier is $12–$15/seat/mo on top of an already-paid Figma/Sketch seat zeplin.io
Syncing very large Sketch files historically required splitting them up, breaking workflows medium.com
RTL text rendering inconsistencies between Figma and Zeplin make it hard for developers to copy text correctly medium.com
Generated code snippets (CSS/iOS/Android) are widely treated as starting points rather than production-grade; teams still hand-rewrite g2.com
Customers must build their own automations (CI hooks, Jira sync, token pipelines) because Zeplin doesn't offer a managed orchestration layer beyond the raw API g2.com