Skip to content
Truto

Unified API

Unified E-Signature API

One standardized interface to read and write electronic signatures data across every provider. 14 unified resources, 5 supported integrations, zero provider-specific code.

https://api.truto.one/unified/e-signature
Start integrating API docs
14

Unified resources

5

Supported integrations

Pass‑through

Real-time, no data storage

Data Model

E-Signature resources

Every resource is normalized across providers. Use the same schema whether your customer is on Adobe Acrobat Sign or DocuSign.

Collections

8 fields Docs →
Collections fields
id string
name string
description string
type string
parent object
urls array
created_at string
updated_at string

Contacts

13 fields Docs →
Contacts fields
id string
first_name string
last_name string
name string
title string
account object
addresses array
email_addresses array
phone_numbers array
tags array
last_activity_at string
created_at string
updated_at string

Document Fields

10 fields Docs →
Document Fields fields
id string
label string
type string
is_read_only boolean
is_required boolean
document object
signing_request object
participant object
created_at string
updated_at string

Documents

The Document object is used to represent documents of e-signature.

10 fields Docs →
Documents fields
id string
name string
signing_request object
urls array
created_by object
status string
scope string
created_at string
updated_at string
last_activity_at string

Field Groups

Represents a group of fields in an E-Signature.

8 fields Docs →
Field Groups fields
id string
name string
label string
description string
entity_type string
status string
created_at string
updated_at string

Fields

Fields represent the attributes defined for various entities in the underlying product. Depending on the underlying product, custom attributes can be defined by a User on various entities like Template, Workflow, etc. is_user_defined attribute within Field can be used to differentiate between custom and system defined Fields.

16 fields Docs →
Fields fields
id string
name string
label string
description string
type string
is_hidden boolean
is_unique boolean
is_required boolean
is_editable boolean
options array
is_user_defined boolean
entity_type string
field_groups array
created_at string
updated_at string
urls array

Groups

The Group object is used to represent collection of Users.

5 fields Docs →
Groups fields
id string
name string
type string
created_at string
updated_at string

Signing Request Statuses

Signing requests go through various stages and each stage is denoted by this resource. Most of the e-signing products have a set state of statuses like draft, sent, created, etc.

4 fields Docs →
Signing Request Statuses fields
id string
name string
created_at string
updated_at string

Signing Requests

The Signing Request object is used to represent signing requests sent.

14 fields Docs →
Signing Requests fields
id string
name string
description string
type string
status object
cancellation_reason string
collections array
groups array
participants array
urls array
created_at string
updated_at string
last_activity_at string
expires_at string

Stages

The stages represent a stage of an opportunity in a workflow.

5 fields Docs →
Stages fields
id string
name string
status string
created_at string
updated_at string

Templates

The Template object is used to represent templates cofnigured for various entities like Documents, messages, etc.

7 fields Docs →
Templates fields
id string
name string
description string
type string
locale string
created_at string
updated_at string

Users

The User object is used to represents a User

19 fields Docs →
Users fields
id string
first_name string
last_name string
title string
name string
username string
emails array
phones array
status string
roles array
organizations array
workspace object
groups array
avatar string
timezone string
languages array
created_at string
updated_at string
urls array

Web Forms

The Web Form object is used to represent web forms of e-signature.

10 fields Docs →
Web Forms fields
id string
name string
groups array
created_by object
owner object
status string
urls array
created_at string
updated_at string
last_activity_at string

Workflows

The Workflow object is used to represent automations configured in the e-sign application.

11 fields Docs →
Workflows fields
id string
name string
description string
type string
status string
created_by object
created_at string
updated_at string
stage object
custom_fields object
urls array

Integrations

5 integrations, one API

Connect to any of these providers through the Unified E-Signature API. Same resources, same schema, same code.

Adobe Acrobat Sign DocuSign Ironclad LinkSquares SpotDraft

How It Works

From zero to integrated

Go live with the Unified E-Signature API in under an hour. No boilerplate, no maintenance burden.

01

Connect your customer’s account

Use Truto’s pre-built auth flows to connect any electronic signatures provider. OAuth, API keys, and custom auth — all handled.

02

Query the unified API

Read and write data through a single, normalized REST API. Same endpoints, same schema, regardless of the underlying provider.

03

Customize with JSONata

Need a field the unified model doesn’t cover? Extend the schema with declarative JSONata mappings — no code deploys, no waiting on us.

From the Blog

E-Signature integration guides

Deep dives, architecture guides, and practical tutorials for building electronic signatures integrations.

Moving Past Checkboxes: Automating Immutable Policy Evidence

Simple checkboxes for policy acknowledgement no longer satisfy enterprise auditors. Learn how to automate legally binding e-signatures using Unified APIs.

Designing Reliable Webhooks: Lessons from Production

Enterprise webhooks are a fragmented mess of HMAC, JWT, and thin payloads. Learn how a unified webhook architecture handles verification and automated enrichment.

Bearer Tokens Were the Easy Part: The Real Challenge of Enterprise Auth

Why modern OAuth 2.0 fails in the enterprise. A deep dive into handling NetSuite’s HMAC signatures and multi-step session auth with programmable headers.

Unified E-Signature API

Start building with the Unified E-Signature API

5 integrations. 14 unified resources. Zero provider-specific code. Ship electronic signatures integrations in hours, not months.

Talk to us