eSignature API Pricing Explained: Credits, Envelopes, and Volume Tiers

eSignature API pricing is easiest to understand in three parts: the usage unit, the volume tier, and any custom enterprise terms.

For Blueink’s current credit-based model, the usage unit is straightforward: 1 credit = 1 envelope. An envelope is the signing transaction being sent, and credits are used to count that production sending volume. Blueink then lowers the published per-envelope rate as customers buy larger credit packages, while Enterprise is available for organizations that need custom limits or terms.

That means estimating your eSignature API cost starts with a simple question: how many production envelopes do you expect your application to send?

Blueink’s live pricing calculator currently starts at 1000 credits and scales through higher-volume packages. You can review the latest numbers directly on Blueink's current API pricing before purchasing.

How eSignature API Credits and Envelopes Work

Credit-based pricing can sound abstract until you separate the two terms.

An envelope describes the signing transaction. A credit is the billing unit used to count that transaction.

What Is an Envelope?

In Blueink, an envelope represents the complete document transaction from preparation through signing and completion.

A single envelope can contain multiple documents, signers, and attachments, provided they are part of the same transaction. The envelope is the entire lifecycle of that document transaction.

So an envelope should not be confused with a single PDF or a single signer.

For example, one agreement package containing three documents that all go out together to two signers can still be one envelope.

What Is an API Credit?

An API credit is the usage unit Blueink uses to track production envelope volume under its current credit-based pricing.

The important distinction is that you are not buying individual signature fields or individual signer actions. You are buying the capacity to send envelopes through the API.

That makes per envelope pricing for eSignature easier to model because the transaction, rather than each individual signature field, becomes the unit you forecast.

How Blueink Credits Work

For Blueink:

1 credit = 1 envelope

So that means, a 1,000-credit package corresponds to up to 1,000 API envelopes, while a 5,000-credit package corresponds to 5,000 envelopes.

Purchased credits do not expire, so customers can use them as needed rather than losing unused credits at the end of a published expiration period.

As of September 2026, the published credit tiers are:

‍

Organizations evaluating production access should confirm with Blueink which commercial structure applies to their account.

How Credit-Based eSignature API Pricing Works

With credit based eSignature pricing, you estimate how many production signing transactions your application is likely to create and buy credits to cover that volume.

The benefit is that the billing unit remains consistent as usage grows.

How Credits Are Calculated

Start with the number of envelopes your application expects to send.

If one production envelope consumes one credit, then the starting calculation is:

Expected production envelopes = credits required

That forecast can be based on monthly, quarterly, annual, or product-lifecycle usage depending on how your application operates.

For SaaS products, for example, usage might depend on how many customers send agreements through your platform. An HR application might estimate envelopes based on new hires. A property platform might base the number on leases or tenant documents.

The important part is to forecast the transactions, not just the number of individual documents.

How Many Envelopes Can You Send With Your Credits?

Because Blueink uses a one-to-one relationship between credits and envelopes:

• 1,000 credits = up to 1,000 envelopes
• 5,000 credits = up to 5,000 envelopes
• 25,000 credits = up to 25,000 envelopes

These are usage examples, not separate pricing claims. The amount you pay depends on the credit tier you purchase.

When Credit-Based Pricing Makes Sense

Credit pricing can work particularly well when your application has measurable or forecastable transaction volume.

Common examples include SaaS platforms adding document signing to an existing product, customer portals that generate agreements, HR systems automating employee documents, or software using Blueink's eSignature API to create signing workflows programmatically.

It can also make scaling easier to model because increased sending volume moves you into larger credit packages with lower published per-envelope rates.

Volume Tiers and Enterprise Pricing

Higher API usage can change the effective cost of each envelope.

Blueink currently publishes progressively lower per-envelope rates as the size of the credit package increases. The listed rate moves from $0.95 per envelope at the 1,000-credit level to $0.24 at 1,000,000 credits.

This is the basic idea behind volume pricing: larger purchases receive a lower effective per-envelope price.

For organizations whose requirements go beyond the published tiers, Blueink also advertises custom Enterprise API packages, including custom limits and additional onboarding/support options. No fixed Enterprise price is published, so the exact commercial terms need to be discussed directly with Blueink.

When evaluating higher-volume API pricing, ask about:

• The credit package that matches expected production usage
• Whether a larger package reduces the per-envelope rate
• Whether custom Enterprise pricing applies at your scale
• Any contractual commitment attached to the quote
• How unexpected growth is handled
• Whether additional product or implementation requirements change the final price

How Embedded eSignature API Usage Works With Credits

Blueink’s embedded signing workflow still creates an API envelope. The developer guide shows that an embedded workflow creates an envelope with the signer configured for embedded delivery and then retrieves an embedded URL for that signing session.

The Embedded Signing API page also displays the same credit-based API envelope calculator used on Blueink’s broader pricing page. There is no separate per-embedded-session transaction price in that calculator.

So in practical terms, the envelope remains the usage unit.

For example, if your SaaS application creates an envelope and lets the customer sign it inside your interface through embedded signing, that is still an API envelope rather than a completely separate category of signing transaction.

Before launching a high-volume embedded implementation, confirm the exact credit treatment attached to your account and any plan-specific feature requirements. 

What to Check Before Choosing an eSignature API Plan

The headline price per envelope is only one part of eSignature API pricing. Before choosing a vendor or package, ask how each of these areas works.

Available Credits

How many production envelopes does the package cover?

For Blueink’s credit model, the relationship is simple: one credit corresponds to one envelope. The current public calculator offers packages from 1,000 through 1,000,000 credits.

Overage Rules

What happens when your available credits run out?

Do not assume that a vendor automatically bills an overage, blocks further sends, or moves you into the next tier. Blueink’s public credit-pricing page does not currently spell out an automatic overage rule for exhausted credit balances, so this is something to confirm before launch.

Minimum Commitments

Is there a minimum purchase or contract commitment?

Blueink’s public calculator currently begins at 1,000 credits, but buyers should confirm whether that represents the minimum purchase available to their account rather than assuming it from the calculator alone.

Credit Expiration

Do unused credits expire?

For Blueink’s current credit offering, the answer is no. The pricing page states that credits have no expiration.

Sandbox and Trial Access

Can your developers build and test before production billing starts?

Blueink supports free API testing. Its API Quick Start guide says trial accounts can send unlimited test envelopes, while its pricing FAQ says customers can test the API at no cost before moving to live production.

That is testing access, not a permanent free production API tier.

Support and Onboarding

What support is included with the package?

Ask whether your purchase includes developer support, implementation assistance, onboarding calls, or a dedicated success contact. Blueink’s Enterprise plans include onboarding and other features, but exact service levels should be confirmed for the package you are buying.

Optional Features and Add-Ons

Are embedded signing, white labeling, authentication, Smart Link Forms, or other features included in your commercial arrangement?

Do not assume every feature is bundled into every pricing structure. Check your required capabilities against the actual quote.

Implementation Costs

Does the vendor charge separately for implementation, migration, custom development, or professional services?

If the public pricing page does not list an implementation fee, that does not automatically mean no such cost can ever apply to a custom deployment. Ask before calculating total cost of ownership.

How to Estimate Your eSignature API Cost

A simple starting framework is:

Expected production envelopes × credit requirement + additional plan or add-on costs

Because Blueink uses 1 credit per envelope, the first part is straightforward.

Step 1: Estimate Envelope Volume

Start with how many production envelopes you expect the API to create.

If your application creates 350 envelopes per month, that is about 4,200 envelopes over 12 months if usage remains steady.

Step 2: Account for Growth

Do not size the package using current volume alone if your product is growing.

Consider expected customer growth, new use cases, new geographies, and planned integrations that may increase signing volume.

Step 3: Consider Peak Usage

Average monthly volume can hide seasonal spikes.

An HR platform may send significantly more envelopes during hiring periods. An education product may spike during enrollment. A tax or financial workflow may be highly seasonal.

The fact that Blueink currently says purchased credits do not expire can make uneven usage easier to model because unused credits are not tied to a published expiration deadline.

Step 4: Include Embedded Signing

If your application creates envelopes for embedded signing, include those transactions in your usage forecast rather than treating them as free simply because the signer never leaves your application.

Worked Example

Suppose your application expects to send 5,000 production envelopes.

At Blueink’s currently published 5,000-credit tier:

5,000 envelopes × $0.75 = $3,750

That example uses the published September 2026 rate of $0.75 per envelope at 5,000 credits.

It does not include any separate custom services, add-ons, or negotiated account terms that could apply.

eSignature API Pricing Comparison: What Should You Compare?

Comparing API prices only by the lowest advertised per-envelope number can be misleading.

A useful eSignature API pricing comparison should look at the whole commercial model:

Plan API Usage Before You Choose a Credit Tier

The easiest way to control eSignature API cost is to understand your transaction volume before buying.

Start with the number of production envelopes your application creates. Add expected growth and seasonal peaks. Include embedded signing transactions. Then compare that forecast against the available credit tiers and any custom Enterprise terms.

For Blueink, 1 credit equals 1 envelope, and the current published volume model reduces the per-envelope rate as credit purchases increase. Credits currently do not expire, and developers can test before going live.

For the latest rates, volume tiers, and production options, see Blueink's API pricing. Developers who want to see it in action can also book a demo. 

Frequently Asked Questions

How Is eSignature API Pricing Calculated?

eSignature API pricing can be based on a usage unit such as envelopes, then adjusted according to volume tiers or custom Enterprise terms.

Blueink’s current credit model uses 1 credit per API envelope, with lower published per-envelope rates as customers purchase larger credit packages. Check Blueink's latest API pricing calculator for current figures.

How Do Credits and Envelopes Work in eSignature API Pricing?

An envelope is the complete signing transaction and can contain multiple documents and signers. A credit is the billing unit used to count API sending volume.

With Blueink, 1 credit = 1 envelope. That means sending 1,000 production envelopes requires 1,000 credits under the current credit model.

How Many Envelopes Can I Send With My API Credits?

Under Blueink’s one-credit-per-envelope model, the number of credits corresponds directly to the maximum number of production envelopes those credits can cover.

For example, 1,000 credits can cover up to 1,000 envelopes, while 5,000 credits can cover up to 5,000 envelopes. The current pricing calculator lists tiers through 1,000,000 credits. 

Is There a Free eSignature API Tier?

Blueink does not advertise a permanent free production API tier.

It does provide free development testing. An API trial account can send unlimited test envelopes, and API testing is available at no cost before moving the API live. Production usage requires a paid arrangement. 

What Should I Check Before Choosing an eSignature API Pricing Plan?

Check the credit-to-envelope ratio, expected production volume, volume-tier pricing, whether credits expire, overage rules, embedded-signing treatment, testing access, support, user limits, optional features, implementation costs, and Enterprise terms.

For Blueink, several of these are publicly documented, including one-credit-per-envelope usage, volume pricing, non-expiring credits, free development testing, and custom Enterprise options. For anything not explicitly listed, confirm the terms with Blueink before purchasing.