BunnyDoc Help Center
Pick your product — E-Signing, Invoicing, or the API — and see exactly what each one covers.
BunnyDoc is two separate products that share one account, one team, and one set of settings. Pick the one you're working in below — each tab tells you what that product covers and where its guides live.
E-Signing covers everything to do with getting a document signed
Upload a document, add signers, place fields, send it, and track it through to a completed, audit-trailed PDF. It also includes document blocks — pricing tables, quote builders, and a Pay button you can drop into the document you're sending, so a signed document can price the work and take payment on the spot.
Envelopes
Create signature requests, add signers, place fields, and track who has signed.
Templates
Reuse documents, fields, and roles — and share them with your team.
Public templates
Share a public link so anyone can request a signing.
Forms
Build and share fillable intake forms and collect responses.
Document blocks
Pricing and invoice tables, quote builders, and Pay buttons inside a signing document.
Document payments
Collect payments while people sign, straight into your Stripe account.
The invoice table in the editor is not the Invoicing product
An invoice table or Pay button you add from the signing editor lives inside that document. It doesn't create an invoice record, an invoice number, or a status you can chase — and it won't show up in the Invoicing product. See Which one do I need? below.
Invoicing covers billing your customers as a standalone business record
Create invoices with their own numbers and statuses, send them, take payment on a public pay page, issue receipts, and chase what's outstanding. Around that sit quotes, credit notes, recurring invoices, your product inventory, and expenses.
Invoices
Create, send, and get paid — plus payments, receipts, and the pay page.
Quotes & credit notes
Quotes, credit notes, and recurring invoices.
Inventory
Products, stock, categories, tags, and discounts.
Expenses
Capture receipts with OCR, email-in, and expense reports.
Only need to price and get paid on a document you're already signing?
You don't need the Invoicing product for that — use document blocks in the signing editor instead.
Two products, two separate APIs
E-Signing and Invoicing each expose their own API, with their own endpoints and their own resources. There is no single combined API — choose the one that matches the product you're integrating with. Authentication and your API credentials are shared across both.
API overview
How the APIs are organised, authentication, and where to get credentials.
E-Signing API
Send documents for signature from your own systems — auth, templates, contacts, and signing links.
Get an access token
The first call every integration makes — exchange your API key for a bearer token.
Invoicing API
Invoices, quotes, credit notes, contacts, inventory, and payments.
Document blocks are part of the E-Signing API
Creating an invoice table inside a signing document is an E-Signing API operation, not an Invoicing API one — same distinction as in the app.
Which one do I need?
Both products can produce something that looks like an invoice. This is the difference:
| Invoice table in the signing editor | The Invoicing product | |
|---|---|---|
| Product | E-Signing | Invoicing |
| Where you build it | The document editor, Doc Blocks tab | The Invoicing section, in its own wizard |
| What it is | Part of the document being signed | A standalone invoice record |
| Invoice number | No | Yes |
| Statuses to chase | Follows the envelope's status | Draft, issued, sent, viewed, paid, overdue, void |
| Customer pay page | Pays during signing | Its own public pay page and receipt |
| Recurring, credit notes, inventory | No | Yes |
| Start here | Document blocks | Invoices |
Rule of thumb: if the money is attached to a document someone is signing, it's E-Signing. If the invoice needs to stand on its own and be chased until it's paid, it's Invoicing.
Account & shared
These apply whichever product you're in.