API
BunnyDoc's APIs — how E-Signing and Invoicing are split into two separate APIs, and where to start.
BunnyDoc's API follows the same split as the app: E-Signing and Invoicing are two separate APIs. They live under one account and share authentication, but they have their own endpoints and their own resources. There is no single combined API.
E-Signing API
Envelopes, signers, fields, templates, document blocks, and payments taken during signing.
Invoicing API
Invoices, quotes, credit notes, recurring invoices, inventory, expenses, and payments.
Choosing the right API
The distinction that trips people up is the same one as in the app — an invoice table built inside a signing document belongs to E-Signing, not Invoicing.
| What you want to do | Use |
|---|---|
| Send a document out for signature | E-Signing API |
| Add a pricing or invoice table to a document being signed | E-Signing API |
| Charge a signer while they sign | E-Signing API |
| Create a standalone invoice with its own number and status | Invoicing API |
| Send a quote or a credit note | Invoicing API |
| Manage products, stock, or expenses | Invoicing API |
Contacts, users, roles, and company settings are shared, so you reach them the same way from either API.
Authentication
Both APIs use the same credentials, issued per company. A request carries the credential and the company it acts on behalf of; every response is scoped to that company.
Keep credentials server-side
API credentials act on behalf of your whole company. Never ship them in a browser, a mobile app, or any client you don't control.
Conventions
- JSON in, JSON out — send and expect
application/json. - Scoped to a company — every resource belongs to one company, and requests never cross company boundaries.
- Same permissions as the app — a credential can only do what its role is allowed to do. See Users & roles.
- Rate limited — sustained bursts are throttled; back off and retry when you're limited.
Endpoint reference
The per-endpoint reference for each API is published in its own section — start with the E-Signing API or the Invoicing API.
How do I create permission templates?
Build reusable sets of permissions you can apply to team members instead of configuring access one key at a time.
E-Signing API
Send documents for signature straight from your own systems — exchange an API key for a token, create envelopes from templates, manage contacts, and retrieve signing links over a simple REST API.