White-Label E-Signature API: Embed Signing in Your App Under Your Brand

What "white-label" means for e-signatures

White-label means your end users never see the signing provider's name. Emails come from your domain. The signing page shows your branding. The signed PDF credits your product, not the third-party API.

There are three approaches to white-label signing, in order of integration depth:

Approach 1: API-first white-labelling with Signbee

With an API-first approach, your backend calls the signing API directly. Your frontend handles the entire user experience. The signing provider is invisible.

// Your SaaS backend — e.g., when a user creates a proposal
const response = await fetch('https://signb.ee/api/send', {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${process.env.SIGNBEE_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    content: proposalMarkdown,
    senderName: 'Acme Proposals',       // Your product name
    senderEmail: 'contracts@acme.com',   // Your domain
    recipientName: clientName,
    recipientEmail: clientEmail,
  }),
});

const { id } = await response.json();
// Save document ID to your database for tracking

Your user sees: "Acme Proposals sent you a document to sign." No mention of Signbee. The signing link goes to signb.ee for the signing ceremony, but the document header shows your sender name and email.

Comparison: white-label e-signature APIs

For a comprehensive pricing and feature breakdown of all 10 major providers, see our best e-signature APIs for developers guide.

Use cases for white-label signing

What to look for in a white-label signing API

1. Custom sender identity — Can you set the sender name and email to your product's brand? This is the minimum viable white-label.
2. No provider watermark — Does the signed PDF contain the provider's logo or only your branding?
3. Custom email domain — Can signing invitation emails come from your domain (e.g., contracts@yourapp.com)?
4. API-first design — Can you build your own UI around the signing flow, or are you forced into an iframe?
5. Pricing at scale — Per-document pricing can become expensive when signing is a core product feature, not an add-on.
6. Audit trail — Does the signing certificate include sufficient evidence for legal compliance?

FAQs