HoneyBook API
No public API, webhooks, or SDK; a community request has been open for over two years. The only path is a Zapier connector gated to Essentials and Premium plans, exposing 6 triggers and 2 actions with no custom fields. Bulk export does not exist, so leaving means manual downloads.
Frequently asked questions
HoneyBook scores F on Supergood's API Report Card. No public API, webhooks, or SDK; a community request has been open for over two years. The only path is a Zapier connector gated to Essentials and Premium plans, exposing 6 triggers and 2 actions with no custom fields. Bulk export does not exist, so leaving means manual downloads.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
HoneyBook is an AI-powered clientflow / client relationship platform for independent service-based small businesses.
Vertical: horizontal CRM / clientflow / business management for service-based independent businesses (categorized as 'misc' here because HoneyBook spans many micro-verticals rather than a single industry). A freelancer or small studio embeds a HoneyBook lead/contact form on their website. New inquiries flow into a project pipeline (Inquiry → Proposal Sent → Booked → Completed).
HoneyBook reports 100,000+ small businesses on the platform, ~55,000 paying customers as of recent disclosures, $74.2M revenue in 2024, $12B+ in lifetime payments processed, and over 25 million client relationships powered since 2013.
Yes, for the independent service business that runs on HoneyBook, this is the system of record for nearly every commercial relationship: the complete client/lead database, every inquiry and lead-form submission, every proposal and signed contract, every invoice and its payment history, every scheduled meeting, every project's stage and timeline, every message and file exchanged through the client portal, automation history, questionnaires, and, critically, the embedded payment rail handling $12B+ in lifetime card and ACH volume.
Founded 2013 in San Francisco / Tel Aviv by Oz Alon, Naama Alon, Dror Shimoni, and Shadiah Sigala after Naama hit vendor-coordination problems planning her wedding.
No public API or webhooks at all, community feature request open 2+ years with no commitment to ship. Apparent contradiction: HoneyBook clearly has an internal API (Zapier uses it) but refuses to expose it publicly, 'Pretty wild they don't have one… (I mean they do since they support Zapier… why not make it public?)'. Full sourced list under Sources below.
Common alternatives include Dubsado, Bonsai, 17hats, Sprout Studio, Studio Ninja, Táve. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
HoneyBook has partial MCP support. A community MCP server in the official MCP registry provides read access to HoneyBook client portal contracts and invoices, with releases as recent as August 2026. HoneyBook has no official server and the coverage is narrow.
Partially. MCP support for HoneyBook exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.