White-Label Update: Branded Editors, Custom Signer Terms, and Your Own Sender Address

Firma.dev is the most white-labelable e-signature API on the market, and three features that shipped recently push that further. Together they let you brand the signing experience end to end: the editor your users see, the consent language they agree to, and the address their notification emails come from. If you're embedding signing into your own product, these close the gaps where Firma.dev's defaults used to show through. For the full how-to on running a white-label setup, the complete guide to a white-label e-signature API covers the end-to-end flow. This post is about what's new.

Brand the embedded editors with five new color controls

The embedded template and signing-request editors, the ones you drop into your own pages, now take five additional color controls. You get accent, accent foreground, canvas, muted surface, and muted text, which join the existing six for eleven total. That's enough to theme the editor chrome to match your product rather than settling for close-enough.

You set them in Settings under Appearance, with a live preview and per-workspace overrides. There's also a contrast warning if you pick an accent and foreground pairing that's hard to read, which saves you from shipping a theme that looks fine in your editor and unreadable to a signer.

Every color is nullable and inherits down the chain: workspace overrides company, company falls back to the Firma.dev default. If you don't set anything, your existing editors render exactly as they did before. On the API side, the five new color_* fields are available on both company and workspace settings endpoints, and the resolved color_palette object now returns eleven keys instead of six.

This shipped in API v1.25.0.

Show signers your own terms and conditions

Custom Signer Terms lets you replace Firma.dev's default consent statement with your own copy. You can set it per language, at either the company or workspace level, so a partner workspace can carry its own brand's terms while your default applies everywhere else. You can attach an optional link to your full terms, and optionally gate signing behind a "require terms acceptance" step that signers have to actively agree to before they proceed.

When a signer accepts, the acceptance is captured server-side along with a content hash of the exact terms they saw. That hash goes into the audit record, so you have a defensible trail of what was agreed to and when, even if you later change the terms text. When nothing is set, signers see the Firma.dev default, so there's no gap during rollout.

The practical uses are straightforward. Legal teams that need their own consent language can enforce it across every signing flow, and partners reselling on top of Firma.dev can show their own brand's terms instead of ours. On the API, the new Signer Terms endpoints support GET, PUT, and DELETE at both levels, and require_terms_acceptance is a boolean on company and workspace settings, nullable on workspace so it inherits the company value.

This shipped in API v1.23.0.

Send from your own address

Notification emails can now come from an address you choose. Custom Email Sender Address lets you set the local-part, the bit before the @, on a verified custom domain. So instead of the default, you can send from noreply@, signatures@, documents@, or whatever fits your product.

It's a company-level default with a per-workspace override, and the workspace value wins where both are set. You do need a verified custom domain first, since this controls the local-part rather than the domain itself. The field accepts 1 to 64 characters: lowercase alphanumeric plus dots, hyphens, and underscores, and it has to start and end on an alphanumeric character. The default local-part is support if you don't set one, so existing senders keep working unchanged.

This is the last visible piece of Firma.dev's identity in a signing flow. Branded editor, your terms, and now your sending address means a signer can go through the entire process without seeing our name anywhere. On the API, it's the email_local_part setting on company and workspace settings.

This shipped in API v1.21.0.

Get started

All three features are live now. Full request and response details are in the API changelog, and the complete white-label e-signature API guide walks through putting them together.

Get started with Firma.dev for free, no credit card required. Pay-as-you-go at $0.029 per envelope (2.9¢ USD), no monthly minimums, no contracts.