Changelog

The API is versioned in its path (/v1). Within v1, changes are additive: new endpoints, new optional request fields, new response fields and new event types. Build clients that ignore fields and event types they do not know. Breaking changes would come with a new version prefix and advance notice here.

2026-10

• The signed PDF in the completion email. The “all parties have signed” email now goes out once the envelope is sealed, to signers, CC recipients and the sender, with the sealed PDF attached (its last pages are the certificate of completion) and a download link that works for 30 days without an account. Organizations choose in the dashboard (Settings → Emails, or completionAttachments on PUT /v1/organization/email-branding): sealed (default), sealed_and_certificate (also the standalone certificate) or none (link only). Files over 7 MB are always sent as a link. If sealing fails, the email still goes out, without the file.

• Signing in 50 languages. The signing page, its consent disclosure and every screen a signer sees are available in 50 languages, including right-to-left Arabic, Hebrew, Persian and Urdu. The page opens in the signer’s browser language, and the signer can switch from the language menu; <bf-signing locale="…"> sets the starting language. A translated disclosure always offers the English text, which is the one that applies, and the signature records which language the disclosure was read in.

• Recipient languages. locale on recipients, CC recipients, viewers or the whole envelope sets the language of the signing page and of every email they receive (requests, reminders, codes, completed, voided, viewer updates). The always-on link page and the viewer status page are translated too. See Languages.

• Send-time options and viewers. POST /v1/envelopes takes optional per-recipient order (reorder steps or sign at the same time, for one envelope), extra cc recipients, reminders and viewers: people who follow the envelope on a read-only status page, with POST /v1/envelopes/{id}/viewers, DELETE /v1/envelopes/{id}/viewers/{viewer} and the public /v1/viewer/* endpoints behind the page. Viewers per envelope are a plan limit (entitlements.features.viewersPerEnvelope). Recipients now carry kind; envelopes carry expiresAt, reminders, viewerDocumentAccess and, on single-envelope responses, viewers.

• Edit text in place. In the designer’s “Edit content” mode, click any text block of an uploaded PDF to change it in place, in the document’s own font (or a metric-compatible fallback), colour and alignment. Stored as a white-out plus a text item sharing a group; text items gain optional face, lineHeight, baseline, padding, group, original and align: "justify". See content edits.

• One upload path. The dashboard’s new-template page has a single upload for PDF and Word files (Word is converted to PDF keeping its layout) next to “Start from blank document”. POST /v1/templates/{id}/import is unchanged.

• Developer docs. This site, with an interactive API reference and the OpenAPI document as JSON and YAML, generated from the API code on every build.

• API v1. Templates (Overlay and Document mode), envelopes with dry runs, idempotency keys and externalId de-duplication, embedded and hosted signing sessions, always-on signing links, Standard Webhooks with retries and replay, PAdES document timestamps, and public verification with Ed25519-signed Merkle anchors.