Build with Bond4Docs

Use paid organization API access for server integrations, or AI Connect through MCP for personal AI assistants. Your permissions follow every request.

One API, familiar workflows

Organization API keys access team management, explicitly shared files, certificate verification, and workspace template forms. Personal document, contact, and template tools are available through AI Connect using MCP. Review and send personal documents in the workspace. Organization automation uses workspace template forms, which send from a member’s account only when their organization allows it.

POST /api/v1/actions/list_shared_documents
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{"organization_id":"YOUR_ORGANIZATION_UUID"}

POST a JSON object matching the operation schema. Responses match the corresponding MCP tool payload, including content blocks where applicable. Keep API secrets on your server. Organization-bound keys can only use team operations and explicitly API-enabled shared files. REST does not accept personal keys or OAuth tokens.

Pay for what you use

Prepaid credits cost $0.01 each. Start with $20 for 2,000 credits, $100 for 10,000, or $500 for 50,000. No subscription, expiry, or automatic top-up. Each credit includes 0.5 MB of response transfer. Storage and Teams are separate.

OperationCreditsPay-as-you-go cost
Lists, metadata, contacts, team actions, verification, embed sessions1$0.01
PDF upload, generation, regeneration, extraction, preview, PDF editing, drafts from templates, workspace form submissions (API or embedded)25$0.25

Authenticated operations consume credits when admitted, including attempts that fail validation or processing. AI Connect MCP calls do not use API credits. Data transfer is metered separately against the included allowance. The OpenAPI specification lists the exact credit cost for every action.

Add API credits

Monthly API plans

small business

$49 / month

10,000 credits

10 GB storage · 5 GB API transfer

medium business

$199 / month

50,000 credits

50 GB storage · 25 GB API transfer

large business

$799 / month

200,000 credits

200 GB storage · 100 GB API transfer

Standard calls use 1 credit; PDF generation, upload, extraction, preview, document regeneration and workspace form submissions use 25. AI Connect through MCP is available without an API purchase. Allowances reset each billing period and stop at the limit, with no automatic overage charges. Teams seats are separate: $9.99 per person per month, adding 10 GB each to shared storage and PDF editing. AI Assistant is coming soon and cannot be purchased yet.

Connect with Bond4Docs

Register an app in your workspace. Users approve specific MCP permissions after signing in to Bond4Docs. Their files remain in their account. AI Connect does not require a Bond4Docs API plan. OAuth tokens work only at /api/mcp; REST uses paid organization API keys. Teams tools still require active membership and sharing permissions.

Register an OAuth app
  1. Register your exact HTTPS callback URL and requested scopes. Keep confidential client secrets on your server.
  2. Generate a random state and PKCE verifier. Store them in your server session. Redirect to the authorization endpoint with the SHA-256 challenge.
  3. Check state on the callback, then exchange the one-time code plus verifier at the token endpoint. Codes last 60 seconds.
  4. Use the access token in the Authorization header for /api/mcp only. REST requires a paid organization API key. Access tokens last one hour. Refresh tokens rotate; store the replacement and revoke on disconnect.
GET /oauth/authorize?response_type=code
  &client_id=YOUR_CLIENT_ID
  &redirect_uri=https%3A%2F%2Fyour-app.com%2Fcallback
  &scope=documents%3Aread
  &state=RANDOM_STATE
  &code_challenge=BASE64URL_SHA256_VERIFIER
  &code_challenge_method=S256
  &resource=https%3A%2F%2Fwww.bond4docs.com%2Fapi%2Fmcp

POST /api/oauth/token
Content-Type: application/x-www-form-urlencoded

grant_type=authorization_code&code=CODE&client_id=CLIENT_ID
&redirect_uri=ENCODED_CALLBACK&code_verifier=VERIFIER
&client_secret=SERVER_CLIENT_SECRET

Public clients omit client_secret. PKCE S256 is mandatory for every client. Discover endpoints at OAuth server metadata. Customers can revoke connections in Settings; developers can disable their entire app.

Signing inside your product

Create a short-lived signing session from your server for one recipient on an already-sent document you own. It expires after 15 minutes and can only be framed by the exact parent origin you supply. Signature fields, phone signing, consent and the audit trail use the same Bond4Docs signing flow.

Authenticate the recipient in your app before returning this bearer URL. The session allows them to act as the chosen recipient. Never expose your API key or OAuth access token to the iframe. Creating a session does not send a document; review and send it in Bond4Docs first.

// AI Connect MCP tool: create_embedded_signing_session
// Use the connected account after verifying the recipient.
// This personal signing-session tool is not an organization REST operation.

{"documentId":"DOCUMENT_UUID","recipientId":"SIGNER_UUID",
 "parentOrigin":"https://your-app.com"}

// Response: {sessionId, url, expiresAt}
// Find recipient IDs in get_document. Keep this URL private.

<iframe id="bond4docs-signing" title="Sign with Bond4Docs"
  src="RETURNED_SESSION_URL" referrerpolicy="no-referrer"
  style="width:100%;height:760px;border:0;border-radius:20px">
</iframe>

window.addEventListener("message", async (event) => {
  const frame = document.getElementById("bond4docs-signing");
  if (event.origin !== new URL(frame.src).origin ||
      event.source !== frame.contentWindow) return;
  if (event.data?.type === "bond4docs:signing-completed" &&
      event.data.sessionId === expectedSessionId) {
    // Ask YOUR server to verify document status through the API.
  }
});

Requires signing-sessions:write. Revoke with revoke_embedded_signing_session and sessionId. Completion messages contain only a session ID; verify status on your server before updating your records. Ordinary signing pages cannot be embedded.

Workspace template forms

Turn an organization template into a form your team fills in from your CRM or internal tools. Each template field belongs either to the sender, who fills it in the form before the document goes out (a start date, a price), or to a signer role such as Client, who completes it when signing. Bond4Docs generates the form from the template. Managers adjust labels, order, defaults and the allowed embedding origins on the template’s Form tab, which also has the embed snippets for that form. A new form starts turned off: a manager turns it on in the Form tab. While it’s off, or while its settings need a manager’s attention after a template change, the schema, sessions and submissions answer 409 with the reason.

Sending is off until your organization turns it on

While Allow sending through the API and embedded forms is off in Organization settings (the default), every submission is saved as a workspace draft in the acting member’s account. The member opens it from Documents › Workspace drafts, adds any missing signers, and sends it. Only the organization owner or a manager can turn the setting on; then submissions are sent immediately from the acting member’s account. Even with sending on, a submission that isn’t ready to send, for example because a signer is missing a name or email, is saved as a draft.

  1. Create an organization API key with the forms:submit scope and keep it on your server. Leaked embed snippets cannot send: every embed needs a session your server creates with that key. The key works for forms only while the person who created it is the organization’s owner or a manager.
  2. When a signed-in user opens the form, create a session for them from your server. Bond4Docs checks that the email belongs to a current member of the form’s organization with access to the template, and that the origin is one of the form’s allowed origins. The embed token lasts 15 minutes; create a new session each time the form is opened.
  3. Render the form in an iframe, or let forms.js request a session from your backend. The frame can only be embedded by the origin in its token.
  4. Listen for messages from the frame. Check the message origin and confirm the result on your server before you update your records.
// Your server, after authenticating your user
POST /api/v1/forms/FORM_ID/sessions
Authorization: Bearer ORGANIZATION_API_KEY
Content-Type: application/json

{"userEmail":"[email protected]","origin":"https://crm.your-company.com"}

// Response, valid for 15 minutes for this member and origin:
// {token, expiresAt, embedUrl, sessionId, sendingEnabled}

<!-- Easiest: the script asks your backend for a session, mounts the
     frame, resizes it and renews the session before it expires.
     Your endpoint returns {token, expiresAt, embedUrl}. -->
<div id="bond4docs-form"></div>
<script src="https://www.bond4docs.com/embed/forms.js" data-form="FORM_ID"
  data-session-url="/your-backend/bond4docs-session"
  data-target="#bond4docs-form" async></script>

// It re-dispatches "bond4docs:form:submitted" and other events
// as bubbling DOM events on the target element.

<!-- Or render the frame yourself from embedUrl -->
<iframe id="bond4docs-frame" title="New service agreement"
  src="EMBED_URL" style="width:100%;border:0"></iframe>

const BOND4DOCS = ["https://www.bond4docs.com", "https://bond4docs.com"];
window.addEventListener("message", (event) => {
  const frame = document.getElementById("bond4docs-frame");
  if (event.source !== frame.contentWindow ||
      !BOND4DOCS.includes(event.origin)) return;
  if (event.data?.type === "bond4docs:form:resize")
    frame.style.height = `${event.data.height}px`;
  if (event.data?.type === "bond4docs:form:submitted") {
    // event.data.documentId, event.data.outcome ("sent" or "draft")
    // and event.data.editUrl. Confirm on YOUR server through the API.
  }
  // Also: "bond4docs:form:ready" and "bond4docs:form:session-expired"
  // (create a new session and post {type:"bond4docs:form:session", token}).
});

Without an embed

Read the form’s schema (scope forms:read), then submit values for an acting member (scope forms:submit). Both requests use the organization API key; the acting user must be a current member of the organization. Leaving out mode saves a draft. Sender fields are keyed by their form key and signers by role. mode: "send" is downgraded to a draft when the organization hasn’t turned sending on, or when the document isn’t ready to send (for example, a signer is missing a name or email). Read outcome in the response, which always states what actually happened. Reuse the same idempotencyKey when you retry, so a retried request can’t create a second document. Send the member’s timeZone (for example America/New_York) so a date field that defaults to “today” gets their date rather than UTC’s; embedded forms send the browser’s.

GET /api/v1/forms/FORM_ID
Authorization: Bearer ORGANIZATION_API_KEY
// Response: {form: {id, title, sendingEnabled, fields, signers, submissionSchema, endpoints}}

POST /api/v1/forms/FORM_ID/submissions
Authorization: Bearer ORGANIZATION_API_KEY
Content-Type: application/json

{"actingUserEmail":"[email protected]",
 "values":{"start_date":"2026-11-02","monthly_price":"499"},
 "signers":{"client":{"name":"Jordan Lee","email":"[email protected]"},
            "ceo":{"include":true}},
 "mode":"send","idempotencyKey":"crm-deal-4821","timeZone":"America/New_York"}

// Response: {submissionId, documentId, outcome, reason, message, editUrl, replayed}
// outcome is what actually happened: "sent" or "draft"

Fixed and optional signers

A signer whose name and email are set on the template, such as a CEO who signs off on every agreement, is added to every document automatically. You send nothing for them, and the form leaves them out unless a manager turns on Show in form. A manager can also make any signer optional: the form shows a checkbox such as “CEO sign-off required”, and headless submissions send signers.ROLE_KEY.include as true or false. Leaving it out uses the form’s default. A signer left out gets no signature request, the fields assigned to them are removed from the document, and the other signers keep their order. include: false on a signer that isn’t optional is a 400, and at least one signer must stay on the document. The form’s schema lists each signer’s hidden and optional settings, and its submissionSchema includes include with its default.

Every submission is recorded with the acting member and the API key or embed that made it, and appears in that member’s documents. A draft is an ordinary Bond4Docs draft: nothing reaches a signer until the member sends it. Removing someone from the organization stops new sessions and submissions in their name. Removing a key’s creator, or giving them a role without management, revokes the organization keys they created; owners and managers can review and revoke every organization key under Team › API keys. A submission that creates a document costs 25 credits, like any other document creation; a rejected submission or a replay costs 1, as do sessions and form reads. Reusing an idempotency key with different values is refused with 409.

Connect an MCP client

https://bond4docs.com/api/mcp

Use AI Connect in user Settings and complete OAuth sign-in. Available to all users without a Bond4Docs API purchase. The endpoint supports protocol versions 2025-11-25 and 2025-06-18. File conversion runs in the browser; saved outputs are available through the API. Organization PDF editing uses edit_organization_pdf with organizations:edit permission. Paid REST PDF operations use 25 API credits. AI Assistant is coming soon. Source PDFs must be explicitly shared for API access.

Predictable permissions

Managers manage people and roles. Files stay private until their owner shares them with a role. Download and external API access are explicit permissions. Removing a member or share revokes subsequent access. Sending through the API and embedded forms stays off until an owner or manager turns it on.

401 means invalid credentials; 402 requires an API plan or sufficient prepaid credits; 403 means missing permission; 413 means storage is full; 429 means a rate or monthly limit. Respect Retry-After. Check state before retrying a write: a lost response does not mean the write failed.