---
title: "White-Label E-Signature API for SaaS Platforms | TurboDocx"
description: "A white-label e-signature API for SaaS platforms: your sender identity on every request, isolated customer organizations with TurboPartner, and pricing that scales per customer."
url: "https://www.turbodocx.com/white-label-esignature-api"
---

# White-Label E-Signature API for SaaS Platforms

> TurboDocx's e-signature API is free for the first 5 signatures a month, then $20 per user per month for unlimited signing in the UI. SaaS platforms add TurboPartner to provision one isolated TurboDocx organization per customer, each with its own users, API key, and signature entitlement, and your own sender name and reply-to email appear on every signature request.

For SaaS platforms and ISVs.

## Agentic Quickstart Skill

Skip the boilerplate: your AI coding agent writes the integration. Install with:

```bash
npx skills add TurboDocx/quickstart
```

[How it works](https://www.turbodocx.com/quickstart.md)

## Key takeaways

- Each customer can get its own TurboDocx organization through TurboPartner, with its own users, API key, and signature entitlement.
- Your sender name and reply-to email go on every signature request and are recorded as the sender in the audit trail.
- Signing can happen inside your product with embedded signing, and each signer can be verified with a passcode or your own identity provider.
- Every signed document is tamper-proof and carries a full audit trail, legally binding under the U.S. ESIGN Act and UETA.
- You can start free and move to Pro when volume grows; partner pricing is set with sales.

## What "white-label" actually means for this API

Two things, specifically. First, every [TurboSign](https://www.turbodocx.com/e-signature-api.md) signature request carries the sender name and reply-to email you configure, recorded as the sender in the audit trail, rather than a shared default address. Second, [TurboPartner](https://www.turbodocx.com/newsroom/turbodocx-launches-partner-portal.md) lets you provision a separate, isolated TurboDocx organization for every customer instead of running all of them through one shared account.

TurboDocx does not currently offer logo or color re-theming of the hosted signing page itself. If your integration needs the signing experience visually re-skinned, ask your TurboDocx contact what is possible for your account before assuming it is included.

The result is that your platform supports e-signatures without your team owning a signing engine, an audit trail, or ESIGN Act and UETA compliance, and without a separate vendor relationship for every customer you onboard.

## Isolate every customer with TurboPartner

A SaaS platform with 200 customers should not run all 200 through one shared TurboDocx organization. TurboPartner creates a separate organization per customer, each with its own users, its own API key, and its own `maxSignatures` entitlement, so you can set signature volume per customer without touching anyone else's account. You manage all of it from a single partner account and one set of SDKs.

```typescript
import { TurboPartner } from '@turbodocx/sdk';

TurboPartner.configure({
  partnerApiKey: process.env.TURBODOCX_PARTNER_API_KEY,
  partnerId: process.env.TURBODOCX_PARTNER_ID,
});

// One isolated organization per customer
const org = await TurboPartner.createOrganization({
  name: 'Acme Corp',
  features: { maxSignatures: 500, maxUsers: 10 },
});

// Issue that customer its own scoped API key
const key = await TurboPartner.createOrganizationApiKey(org.data.id, {
  name: 'acme-production',
  role: 'admin',
});

// key.data.key is the full secret, shown only on creation
```

## What your end customer sees

The signature request email shows your `senderName`, and replies go to your `senderEmail`. Both are recorded as the sender in the audit trail. The document they sign is legally binding under the U.S. ESIGN Act and UETA.

With [embedded signing](https://www.turbodocx.com/embed-electronic-signature.md), the signing page opens inside your product in an iframe, a new tab, or a redirect, and no signing-link email is sent. Your server asks TurboSign for a signing URL when the signer is ready, so your API key never reaches the browser. An admin turns embedded signing on for each organization and lists the domains allowed to show the signing page. The details are on the embedded signing page and in the [createSigningUrl guide](https://www.turbodocx.com/guides/embed-signing-with-createsigningurl.md). Because no email link proves who is at the screen, you verify each embedded signer with an [email or SMS passcode, or with your own identity provider](https://www.turbodocx.com/electronic-signature-identity-verification.md), and the result is recorded on the certificate of completion.

## Plain API key vs. a TurboPartner white-label setup

A single API key works for a platform with one tenant, or for testing. Once you have multiple customers who should not see each other's data, TurboPartner is the difference between one shared bucket and real per-customer isolation.

| Dimension | Plain API key | TurboPartner white-label |
| --- | --- | --- |
| API access | One shared API key across your whole platform | One API key per customer organization, issued by you |
| Data isolation | All customers' documents and signers share one organization | Each customer gets its own organization: own users, own documents |
| Signature entitlement | One shared account-level plan for every customer | `maxSignatures` set per customer organization |
| Who provisions it | You, by hand, in the TurboDocx UI, one time | You, programmatically, one `createOrganization` call per customer |

## Pricing at scale

A direct TurboDocx account starts free with 5 signatures a month, no credit card required. Pro is $20 per user per month with unlimited signing for named users in the UI; API-key access on Pro includes 60 signatures a month by default.

If you are building a SaaS platform, TurboPartner is a separate path: you provision one TurboDocx organization per customer and set that organization's own `maxSignatures` entitlement, so volume is decided per customer instead of by a single shared cap. [Talk to sales](https://www.turbodocx.com/demo) about pricing across many customer organizations, or see the standalone-account breakdown on the [pricing page](https://www.turbodocx.com/pricing.md).

## Why SaaS platforms build on TurboDocx

- Sender name and email on every request and audit trail entry, set by you
- TurboPartner: an isolated organization, API key, and entitlements per customer
- Legally binding under the U.S. ESIGN Act and UETA, with a full audit trail
- Developer-first REST API and SDKs for JavaScript/TypeScript, Python, PHP, Go, Java, and Ruby
- Document generation and signing in one platform, not two vendors to integrate
- Open source SDKs on GitHub, so you can see exactly what your integration calls

Building the integration itself? Start with the [e-signature API](https://www.turbodocx.com/e-signature-api.md) overview, the [developer hub](https://www.turbodocx.com/developers.md), or pair it with [document generation](https://www.turbodocx.com/products/turbodocx-templating.md) if you are also generating the documents you send for signature.

## Frequently Asked Questions

### What does white-label mean for an e-signature API?

For TurboDocx it means two things: the sender name and reply-to email you configure appear on every signature request and are recorded as the sender in the audit trail, and TurboPartner can provision one isolated TurboDocx organization per customer instead of a single shared account. TurboDocx does not currently offer logo or color re-theming of the hosted signing page itself; ask sales if your integration needs that.

### How do I integrate e-signatures into my SaaS platform for multiple customers?

One createOrganization call per customer provisions an isolated TurboDocx organization through the TurboPartner API, and a second call, createOrganizationApiKey, issues that organization its own API key. Set a maxSignatures entitlement per organization so one customer's usage cannot consume another's, and each organization's users and documents stay separate.

### How much does an embedded e-signature API cost?

The free tier includes 5 signatures a month with no credit card required. Pro is $20 per user per month with unlimited signing for named users in the TurboDocx UI, and API-key access on Pro includes 60 signatures a month by default. If you provision customers through TurboPartner, each organization carries its own maxSignatures entitlement; talk to sales about pricing across many customer organizations.

### Can I isolate each of my customers' signing data?

Yes. TurboPartner provisions one TurboDocx organization per customer, each with its own users, API key, storage, and signing history, separate from every other customer's. One organization's documents and signers are never visible from another's, and you manage all of them from a single partner account.

### What does my end customer see when they sign?

They see your sender name on the signature request, and replies go to your reply-to email. Both are recorded as the sender in the audit trail. They sign on TurboDocx's hosted signing page, or inside your own app with embedded signing once an admin turns it on for the organization and allows your domain. The signature is legally binding under the U.S. ESIGN Act and UETA.

## Ship e-signatures under your own identity

Start free with a single API key, or talk to sales about TurboPartner and volume pricing for your customer base. [Explore TurboPartner](https://www.turbodocx.com/why-partner.md).

[Get Started Free](https://app.turbodocx.com)