Create Fully Branded Signing Experiences with Blueink
A Signing Experience That Feels Like Your Own Product
Put your logo at every step
With Blueink’s Signing Brands, your logo is featured prominently in emails and across the signing experience, making each signing session feel like part of your own product.
.png)
Guide users through a smooth journey
Set custom messages, choose where users go after signing, and embed the signing session directly inside your app to keep everything consistent and familiar.
Create Seamless Signing Experiences with Embedded Signing
For full control, keep signers inside your application using Blueink’s embedded signing. Present the signing experience in an iframe so users never leave your app while maintaining a consistent, branded flow.
Smart Pricing for Every Business Size
Volume Discounts
API Envelopes
$0.95
53% DISCOUNT
What’s Included
Volume Discounts
No Expiration
Free to Test
Up to 5 users
Developer dashboard
API Envelopes
Price per Envelope
Discount
Up to 1,000
$0.95
Scale pricing as you grow
5,000
$0.75
Save 21%
25,000
$0.60
Save 37%
100,000
$0.45
Save 53%
250,000
$0.35
Save 63%
500,000
$0.28
Save 71%
1,000,000
Best Value
$0.24
Save 75%
Up to 1,000
Scale pricing as you grow
$0.95
per envelope
5,000 Envelopes
Save 21%
$0.75
per envelope
25,000 Envelopes
Save 37%
$0.60
per envelope
100,000 Envelopes
Save 53%
$0.45
per envelope
250,000 Envelopes
Save 63%
$0.35
per envelope
500,000 Envelopes
Save 71%
$0.28
per envelope
1,000,000 Envelopes
Best Value
Save 75%
$0.24
per envelope
FAQs
Blueink supports Signing Brands, Custom Messaging, Embedded Signing and Custom Redirect URLs, which can be used in conjunction to create seamless, branded signing experiences in your App or Integration. In addition, if your App handles its own notifications to Signers, you can suppress the built-in Blueink Signer notifications, giving you additional control over the signing experience.
Yes. You can define a specific signing_complete_redirect URL for each Signer in an Envelope. This URL determines where the signer will be redirected after completing the signing session. It takes priority over any default redirect configured at the account or Signing Brand level. This allows you to tailor the post-signing experience for each envelope, such as sending users to a thank-you page, onboarding screen, or client dashboard.
In addition, when building an Embedded Signing workflow, the embedded signing iFrame emits events to the parent window, so that your App can know when a signing session has started or ended, so that your App UI can react appropriately.
All signing sessions occur at a Blueink URL (e.g. sign.blueink.com), to ensure the integrity of the signing process. However, Developers can embed the signing experience directly into their own website or application using an iframe, allowing signers to complete the process within your custom domain. This creates a fully branded experience while keeping Blueink’s secure signing infrastructure in the background.
No. Users cannot upload or configure logos directly through the API. Logos must be uploaded and managed inside your Blueink account under the Signing Brands section. However, once a Signing Brand is configured in Blueink, you can configure any Envelope created via the API to Signing Brand. In addition, you can set default Signing Brands on the Team and Account levels, which will apply to Envelopes created via the API.
No. Even when white-labeled, all eSignature data remains stored and processed within Blueink’s secure infrastructure. The platform maintains complete compliance with ESIGN, UETA, and GDPR standards, ensuring that branding changes do not affect the legality or security of your documents.
.svg)
.svg)
.png)
.svg)
.svg)
