--- title: DocuSign API Integration on Truto slug: docusign category: Cloud Storage canonical: "https://truto.one/integrations/detail/docusign/" --- # DocuSign API Integration on Truto **Category:** Cloud Storage **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Billing** — Billing object represents a Bill - **Licenses** — Licenses represent concepts like user seats in apps that support them - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. - **Utilization** — Utilization object represents utilization reports. ### Unified E-Signature API - **Collections** — - **Contacts** — - **Document Fields** — - **Documents** — The Document object is used to represent documents of e-signature. - **Groups** — The Group object is used to represent collection of Users. - **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. - **Signing Requests** — The Signing Request object is used to represent signing requests sent. - **Templates** — The Template object is used to represent templates cofnigured for various entities like Documents, messages, etc. - **Users** — The User object is used to represents a User ## How it works 1. **Link your customer's DocuSign account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach DocuSign.** The Proxy API is a 1-to-1 mapping of the DocuSign API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Automate contract generation from your app's workflow stages** — SaaS platforms can trigger DocuSign signing requests automatically when a record hits a specific stage — like sending an offer letter when a candidate reaches 'Offer' in an ATS, or a lease when a tenant is approved. This eliminates manual document prep and reduces time-to-signature. - **Track signing progress in real time within your product** — By syncing signing request statuses, your app can show users exactly where each agreement stands — sent, delivered, viewed, signed, or declined — without requiring them to switch to DocuSign. This powers conditional logic like auto-advancing deal stages or triggering follow-up reminders. - **Pre-fill documents with CRM or app data to eliminate duplicate entry** — SaaS companies can map their internal data (customer name, deal amount, start date) to DocuSign template fields, so end users never have to re-type information that already exists in your system. This reduces errors and dramatically speeds up document turnaround. - **Archive signed documents back to your platform automatically** — After a signing request is completed, your app can pull the finalized PDF and attach it directly to the relevant record — an employee profile, a deal, a tenant file — giving users a single source of truth without manual downloads. - **Manage DocuSign user permissions and envelope utilization at scale** — For enterprise customers with shared DocuSign accounts, your platform can surface which users have active licenses, their roles, and how many envelopes have been consumed — helping admins govern access and manage billing from within your product. ## What you can build - **Template-powered document generation** — Let users select from their DocuSign templates, auto-populate document fields with data from your app, and send signing requests — all without leaving your UI. - **Real-time signing status dashboard** — Display a live view of all outstanding and completed signing requests with statuses like sent, delivered, completed, declined, or voided, synced from DocuSign via Truto's Unified E-Signature API. - **Multi-party routing with contact management** — Build workflows that send agreements to multiple signers (e.g., tenant, co-signer, guarantor) in a defined routing order by leveraging contacts and groups from DocuSign. - **Signed document write-back to entity records** — Automatically fetch completed PDFs and certificates of completion from DocuSign and attach them to the corresponding record in your application — a candidate, deal, property, or loan. - **License and utilization monitoring for admins** — Surface DocuSign user roles, license assignments, and envelope utilization data so your customers' admins can manage permissions and track usage without switching tools. - **Stage-based automation triggers on signature events** — Advance records through your app's pipeline automatically — move a deal to 'Closed Won' or a candidate to 'Hired' — when a signing request status changes to completed. ## FAQs ### What authentication method does the DocuSign integration use? DocuSign supports OAuth 2.0 (Authorization Code Grant) for user-level authentication. Truto handles the full OAuth flow, token refresh, and credential storage so your end users can connect their DocuSign accounts securely without you managing tokens. ### Which Truto Unified APIs cover DocuSign? DocuSign is supported through two Unified APIs: the Unified E-Signature API (covering Templates, Document Fields, Documents, Collections, Contacts, Groups, Signing Requests, Signing Request Statuses, and Users) and the Unified User Directory API (covering Users, Roles, Licenses, Billing, and Utilization). ### Does Truto handle DocuSign's API rate limits and pagination? Yes. Truto manages rate limiting, retry logic, and cursor-based pagination behind the scenes. Your application makes standard Unified API calls and Truto handles the underlying DocuSign API constraints transparently. ### Can I read and write signing requests, or is the integration read-only? The Unified E-Signature API supports both reading and creating signing requests, as well as tracking their statuses. Specific write capabilities for other resources depend on the underlying DocuSign API permissions and can be confirmed during setup. ### How does the integration handle multi-account DocuSign setups? When an end user authenticates, Truto captures the associated DocuSign account context. For organizations with multiple DocuSign accounts, the integration respects the account scope selected during the OAuth consent flow. ### What if I need a DocuSign capability that isn't covered by the current Unified API resources? Truto builds integration tools on request. If you need support for additional DocuSign endpoints — like embedded signing URL generation or specific webhook event types — you can request them and the Truto team will scope and build them for your use case.