The API Report CardAPI Index
Bonsai

Bonsai API

Freelance finance contracts · hellobonsai.com

A REST API exists but is treated as integration plumbing: API keys generate self-serve from Settings, yet there is no developer portal, published spec, or SDKs. Real integration runs through Zapier (proposal, contract, and invoice triggers); webhooks are Zapier-mediated rather than first-party.

Last verified: July 2026Other
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA REST API exists with JSON and account API keys, though it is positioned as plumbing for Zapier rather than a platform.
AccessGOODAPI keys generate self-serve from Settings, Integrations on any account.
CoverageMIXEDProposals, contracts, invoices, deals, and tasks surface as Zapier triggers; direct endpoint coverage is undocumented.
AuthMIXEDAccount-generated API keys are the only primitive; no OAuth app model or scopes.
Docs & DXMIXEDDocs live in the Help Center and Zapier's pages; no developer site, OpenAPI spec, or SDKs, and webhooks are Zapier-mediated.
StabilityMIXED
Supergood: Bonsai has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Bonsai scores C on the API Report Card. A REST API exists but is treated as integration plumbing: API keys generate self-serve from Settings, yet there is no developer portal, published spec, or SDKs. Real integration runs through Zapier (proposal, contract, and invoice triggers); webhooks are Zapier-mediated rather than first-party.

Tried to integrate with Bonsai?