eSignature API Example for SignNow Workflows

Award-winning eSignature solution

What an eSignature API example does

An eSignature API example shows how software sends a document, routes it to one or more signers, captures their consent, and stores the signed record with an audit trail. In practice, the application creates or uploads a file, adds fields such as signature and date, sends a signing link or embedded request, and then records each action. For U.S. transactions, the process supports ESIGN and UETA requirements by linking the signature to the signer, the document, and the time of signing.

Why the API example matters

It reduces manual handling, speeds document turnaround, and creates records that can support enforceability under ESIGN and UETA when consent, intent, and attribution are documented.

Why teams look for DocuSign alternatives

Common implementation pain points

Mapping document fields correctly can take time when the source file changes across templates or versions.
Signer authentication can be too weak for higher-risk transactions if only email access is used.
Audit records may be incomplete if IP data, timestamps, or delivery events are not retained.
Compliance gaps appear when retention, consent, or BAA requirements are not configured for the document type.

Real estate

Real estate teams use it for leases, disclosures, and rental applications that need fast turnaround.

Healthcare and finance

Healthcare and finance teams use it for consent forms, approvals, and regulated recordkeeping.

People who benefit most

Operations leaders at companies like Tech Data use signNow to keep internal and external document flows moving without adding manual follow-up. They usually need a system that fits sales, procurement, and service paperwork while keeping signatures tied to the right records and teams.
NetSuite operations specialists, such as the Xerox team cited by signNow, benefit when signatures must match ERP-driven document logic. They often need routing rules, field control, and consistent formats so approvals, orders, and customer documents stay aligned with back-office systems.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

API routing

Send documents through an API flow that keeps signing steps organized, traceable, and easier to automate across teams and systems.

Audit trail

Capture signer actions, timestamps, and document history so the final record supports review, audit, and dispute handling.

Templates

Use templates to standardize repeat agreements, reduce setup time, and keep field placement consistent across transactions.

Mobile access

Support mobile signing so recipients can review and sign on phones, tablets, or desktops without extra steps.

Signer checks

Apply signer authentication options to match the risk level of the document and the compliance needs of the workflow.

Record integrity

Store completed files in a format that preserves the signed version and the evidence attached to it.

Integration options that fit the workflow

Connected systems move documents, signer data, and completed records between the tools teams already use every day.

How the signing flow works

The flow starts with document preparation, then moves through routing, signing, and record storage in a fixed sequence.

Create: Upload or generate the document in signNow.
Prepare: Add fields, recipients, and signing order.
Route: Send the signing request and track status.
Complete: Store the completed file with its audit history.

Quick setup steps

Use a short setup sequence to prepare the document, define signers, and send the request.

Start the file:
Create a document or choose a reusable template.
Add fields:
Place signature, date, and required form fields.
Assign signers:
Set recipients and signing order.
Send and track:
Send the request and monitor completion.

Setting	Recommendation
Authentication method	SMS OTP
Signature type	SES
Audit trail	UTC timestamps
Document retention	6 years (HIPAA 45 CFR 164.530(j)(2))
Encryption	TLS 1.2/1.3 and AES-256

Platform and system requirements

The API and signing experience work across major browsers and operating systems when the device can reach a secure TLS connection.

Desktop browsers Chrome, Firefox, Safari, and Edge.
Operating systems Windows, macOS, iOS, and Android.
Security transport TLS 1.2 or TLS 1.3.

Managed deployments often pair browser access with SSO, device controls, and retention rules. Mobile signing is supported on iOS and Android, while desktop users can work in Chrome, Firefox, Safari, or Edge.

Security and data protection

Encryption in transit:

TLS 1.2/1.3 in transit

Encryption at rest:

AES-256 at rest

SOC 2 Type II:

SOC 2 Type II available

ISO 27001:

ISO 27001 certified

HIPAA support:

HIPAA support with BAA

Privacy standards:

GDPR and eIDAS aligned

Enterprise operations

Tech Data used signNow to improve internal and external customer service while increasing speed to revenue.

Faster routing across teams
Less manual follow-up

The workflow reduced document delays and kept approvals moving across internal and customer-facing processes. That matters for teams that need speed without losing control of the signed record or the process history.

NetSuite operations

Xerox used signNow with NetSuite to get the right signatures on the right documents in the right formats.

NetSuite-based routing
Format-specific signature control

The integration helped align signatures with ERP-driven document rules. It is useful when approvals depend on document type, routing logic, and consistent record handling across finance, operations, and customer workflows.

Best practices for implementation

A stable setup depends on clear templates, appropriate authentication, and records that stay available for review.

Standardize repeat documents

Use templates for recurring agreements so field placement, signer order, and required data stay consistent across sends. This reduces setup errors and makes the API flow easier to maintain as document versions change.

Match authentication to risk

Match authentication strength to document risk. Use stronger verification for regulated or high-value transactions, and keep the method aligned with the evidence you may need later in a dispute or audit.

Preserve signing evidence

Keep the audit trail complete by retaining timestamps, signer identity details, delivery events, and document hashes. Missing evidence can weaken attribution and make later review harder for legal or compliance teams.

Define retention up front

Set retention rules before launch so signed records stay available for the required period. Healthcare records, for example, may need 6 years under HIPAA retention rules.

FAQ and troubleshooting

These answers focus on plan limits, compliance requirements, and the evidence needed for U.S. electronic signature workflows.

signNow Business starts at $8/user/mo billed annually. It includes legally binding eSignatures, audit trails, templates, mobile apps, ISO 27001, SOC 2, and GDPR support.

HIPAA workflows require a BAA. signNow’s HIPAA support is tied to that agreement, and signed records should follow the 6-year retention rule in 45 CFR 164.530(j)(2).

For stronger signer verification, use SMS OTP or other higher-assurance methods instead of email-only access. U.S. enforceability depends on attribution, consent, and evidence, not on a specific signature style.

If a document needs stronger evidentiary support, keep the audit trail intact. signNow records timestamps, signer activity, and document history, which helps with ESIGN and UETA defensibility.

Bulk send is included in Business Premium, which is priced at $15/user/mo annually. If you need mass distribution, choose that plan instead of the Business tier.

For regulated records, keep encryption enabled and use the compliance features tied to your workflow. signNow supports TLS 1.2/1.3 in transit, AES-256 at rest, SOC 2 Type II, and ISO 27001.

signNow	DocuSign	Adobe Sign	PandaDoc
Audit trail	Yes	Yes	Yes
HIPAA support	Yes	Yes	Yes
Starting price	$8/user/mo	$15/user/mo	$14/user/mo
Envelope cap	No cap	100/user/year	Not verified

Setup day 1:

Create the account and configure the first workflow.

First send:

Send the document after fields and recipients are set.

Team onboarding:

Add users after the first workflow is confirmed.

Free trial:

7-day free trial, no credit card required.

HIPAA retention:

6 years from creation or last effective date.

UETA adoption:

49 states, the District of Columbia, Puerto Rico, and the U.S. Virgin Islands have adopted UETA.

Business plan:

$8/user/mo billed annually.

Enterprise review:

Confirm BAA, SSO, and retention before rollout.

Risks of poor implementation

Weak attribution

Document may be harder to enforce.

Incomplete logs

Audit evidence may be challenged.

Missing BAA

HIPAA records may fail review.

No consent record

Signed file may be disputed.

Signer authentication:

Verifies the signer before the action is recorded.

Timestamp capture:

Stores the signing moment in UTC.

Document hashing:

Calculates a hash for the document version.

Tamper-evident sealing:

Locks the record against later changes.

Event history:

Keeps the event history tied to the file.

Audit export:

Exports the audit trail for review or evidence.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free trial	7-day trial	Not verified	Not verified	Not verified	Not verified
Bulk send	Business Premium	Not verified	Not verified	Not verified	Not verified
Audit trail	Included	Included	Included	Included	Included
Envelope cap	No cap	100/user/year	Not verified	Not verified	Not verified

28M+Documents signed

13+Years in business

4.6/5Average G2 rating