In your stack

Create a document from your own system, and hear back when it is signed.

The API covers the useful half: make a document, get it back as a PDF, send it. Everything else arrives as a signed webhook you can point anywhere.

POST /api/v2/docs
Authorization: Bearer pb_live_…
{
  "template_id": "tpl_sow",
  "client": "Northwind Traders",
  "send": true
}
webhookdocument.completed → your endpoint, signed
01

API v2

GET and POST /api/v2/docs to create from a template or from a brief, GET /api/v2/docs/{id}?pdf=1 for the PDF, POST /api/v2/docs/{id}/send, and GET /api/v2/templates. Keys are pb_live_ prefixed.

02

Signed webhooks

Document events go out as signed outbound webhooks, so Zapier, Make or n8n can carry them wherever you need without a bespoke integration.

03

Slack, HubSpot and Pipedrive directly

A Slack incoming webhook, a HubSpot private-app token or a Pipedrive API token, driven by the same document events.

Plan: The API, webhooks and integrations begin on Pro.

What it is not: There is no Salesforce integration.

Call ends. Proposal sent. In seconds.

Three documents a month, free. No card.

Start free