The API Report CardAPI Index
THE API REPORT CARD / Marketing & Sales / Pastel
Pastel

Pastel API

usepastel.com

No public REST API. Pastel's programmatic surface is a Zapier trigger on new comments plus a per-canvas outbound webhook that POSTs comment exports. The webhook has no documented signing, retry policy, or event types beyond comment export.

Last verified: August 2026Marketing & SalesNO MCP
API GRADE
F
VERIFIED AUG 2026

SCORECARD

ExistenceFAILNo REST API, documented endpoints, or developer portal; the surface is one outbound webhook and a Zapier trigger for comments.
AccessFAILOnly the account owner's personal token exists; no partner program, developer signup, or app registration is available.
CoverageFAILOnly surface is an outbound comment export webhook and a Zapier trigger; no canvas CRUD, comment retrieval, or user endpoints.
AuthFAILWebhook POSTs carry no HMAC signing, and the single personal API token forces rewiring every Zap on rotation.
Docs & DXFAILDocumentation is two help-center articles; no API reference, event taxonomy, retry semantics, SDKs, or OpenAPI spec.
StabilityMIXED
MCPNONENo official or community MCP server for Pastel was found in the MCP registry or on GitHub; repositories matching the name relate to unrelated projects. VERIFIED 2026-08
See what enterprise platforms do have MCP servers →
MORE FROM THE REPORT CARD
BugHerdB+Marker.ioFZiflowB17hatsC
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Pastel scores F on Supergood's API Report Card. No public REST API. Pastel's programmatic surface is a Zapier trigger on new comments plus a per-canvas outbound webhook that POSTs comment exports. The webhook has no documented signing, retry policy, or event types beyond comment export.

Tried to integrate with Pastel?
SOURCES
No public REST API reference, usepastel.com has no /docs, /developers, or /api documentation site; apitracker.io's profile is largely empty apitracker.io ↗
Webhook documentation does not specify any authentication or HMAC signing mechanism, receivers can't cryptographically verify Pastel-origin POSTs help.usepastel.com ↗
Webhook delivery is only documented for the comment-export event; no published event taxonomy for canvas-created, canvas-approved, user-added, etc. help.usepastel.com ↗
No documented retry/backoff or `Retry-After` semantics on webhook failures, integrators must guess delivery behavior help.usepastel.com ↗
No OAuth app flow or scoped developer tokens, Zapier auth uses a single personal API token from the profile page, so rotation requires updating every connected Zap by hand help.usepastel.com ↗
Native integration set is one platform deep (Asana), every other PM/messaging destination requires Zapier or a custom webhook receiver asana.com ↗
No SDKs in Node/Python/Ruby/Go/.NET; no community libraries on GitHub for Pastel's surface; integrators write raw HTTP handlers from scratch apitracker.io ↗
No OpenAPI/Swagger spec published, API clients can't be code-generated, and there is no canonical schema for the webhook payload apitracker.io ↗
Zapier's per-task billing creates hidden marginal cost, high-volume comment streams (busy agency portals) burn Zapier Task quota and force expensive Zapier tier upgrades help.usepastel.com ↗
No developer portal or app-marketplace registration model, third parties cannot publish a one-click 'connect Pastel' OAuth app usepastel.com ↗
Webhook payloads include sensitive screenshot URLs and user metadata of in-progress client sites; no documented PII redaction or DLP controls before egress help.usepastel.com ↗
Comment-export is the only documented outbound data path, there's no documented way to programmatically read canvas state, approval history, or audit trail back out for migration/archive help.usepastel.com ↗
Free plan is restricted to 1 active canvas at a time; agencies juggling multiple client projects hit the wall immediately feedbucket.app ↗
72-hour commenting window on the free plan forces upgrade for any real client cycle medium.com ↗
Per-user pricing scales aggressively, $29/user/mo on top of base plan; agencies with 5–10 reviewers see bills jump quickly huddlekit.com ↗
Solo plan ($29/mo) capped at 3 premium canvases; jump to Studio ($99/mo) is steep with little middle tier commentblocks.com ↗
Lacks deep technical features (no built-in Kanban, no time-in-status, no SLA reporting); teams outgrow it as projects mature feedbucket.app ↗
Limited dashboard and reporting, hard to get cross-canvas visibility for agencies running 20+ active client projects commentblocks.com ↗
Comment list becomes unwieldy past 30–40 comments per canvas; preview text is insufficient to distinguish them, forcing repeated open/close g2.com ↗
Performance can be slow, canvas loading and comment-list scrolling lag on heavy projects g2.com ↗
Proxy-based snapshot approach struggles with auth-gated staging environments, SPAs with aggressive client routing, and sites that block iframe-style embedding bugherd.com ↗
Mobile/responsive feedback is functional but weaker than desktop; some breakpoints render inconsistently inside the canvas snapfeed.app ↗
No built-in task management / Kanban board, feedback has to be exported to Asana/Trello/ClickUp to be actionable bugherd.com ↗
Native integration set is thin, only Asana is first-party; other PM tools require Zapier glue help.usepastel.com ↗
No enterprise-grade plan tier or custom pricing publicly advertised; large agencies are forced into seat sprawl capterra.com ↗
Audit trail and approval-history features are usable but lighter than Filestage/Ziflow for regulated creative workflows huddlekit.com ↗
© Supergood Systems, Inc.