--- title: LinkSquares API Integration on Truto slug: linksquares category: Default canonical: "https://truto.one/integrations/detail/linksquares/" --- # LinkSquares API Integration on Truto **Category:** Default **Status:** Beta ## Unified APIs ### Unified E-Signature API - **Documents** — The Document object is used to represent documents of e-signature. - **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. - **Stages** — The stages represent a stage of an opportunity in a workflow. - **Templates** — The Template object is used to represent templates cofnigured for various entities like Documents, messages, etc. - **Workflows** — The Workflow object is used to represent automations configured in the e-sign application. ## How it works 1. **Link your customer's LinkSquares 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 LinkSquares.** The Proxy API is a 1-to-1 mapping of the LinkSquares 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 - **Enforce contract compliance before releasing spend** — Spend management and AP automation platforms can verify that an active, signed agreement exists in LinkSquares before approving purchase orders or issuing virtual cards — ensuring every dollar spent is backed by an executed contract. - **Accelerate deal velocity from your RevOps platform** — Sales execution tools can let AEs generate contract drafts directly from their workflow by pulling LinkSquares templates and populating agreement fields with deal data, so reps never leave their primary tool while Legal retains full control over templates and approvals. - **Auto-populate risk dashboards with AI-extracted contract metadata** — GRC and risk management platforms can sync Smart Values from executed contracts in LinkSquares — renewal dates, SLA penalties, governing law — to surface legal risk automatically without manual document review. - **Keep CRM records in sync with contract lifecycle stages** — Revenue platforms and CRMs can track contract progression (Drafted → In Review → Out for Signature → Executed) by reading agreement stages from LinkSquares, giving sales and finance teams real-time visibility into deal status. - **Centralize e-signature workflows across multiple CLM tools** — B2B SaaS companies whose customers use different CLM platforms can offer a single integration experience by mapping LinkSquares to Truto's Unified E-Signature API alongside other providers, reducing engineering effort per connector. ## What you can build - **Template-driven contract generation** — Let your users select a LinkSquares template, inject deal-specific fields, and generate a contract draft without leaving your application. - **Real-time contract stage tracker** — Display the current agreement status — from draft through execution — inside your product by reading LinkSquares workflow stages. - **Smart Values sync for automated risk scoring** — Pull AI-extracted metadata like renewal dates, opt-out clauses, and payment terms from signed contracts into your platform's dashboards. - **Intake queue for third-party paper** — Allow end users to push vendor-provided documents into LinkSquares for legal review directly from your procurement or onboarding workflow. - **Agreement hierarchy browser** — Surface parent-child relationships between MSAs and their associated SOWs so users can navigate the full contract structure from within your app. - **Approval task integration** — Surface pending LinkSquares review tasks inside your product's notification center, enabling approvers to act without switching tools. ## FAQs ### What Unified API does Truto use for LinkSquares? LinkSquares maps to Truto's Unified E-Signature API, which covers Documents, Fields, Stages, Templates, and Workflows. This lets you read and write against LinkSquares using the same schema you'd use for other e-signature and CLM providers. ### Are there pre-built Truto tools for LinkSquares today? LinkSquares tools are built on request. Once you signal demand, Truto's team configures the connector — handling auth, pagination, and API-specific quirks — so you don't have to. ### How does LinkSquares split its API surface? LinkSquares exposes two distinct API modules: the Finalize API for pre-signature workflows (drafting, templates, intake) and the Analyze API for post-signature operations (Smart Values metadata extraction, agreement hierarchy). Truto normalizes both into the Unified E-Signature API model. ### Can I access LinkSquares custom fields and AI-extracted metadata? Yes. Agreement Detail Fields (custom metadata injected before signing) map to the Fields resource, and Smart Values (AI-extracted data points from executed contracts) are accessible through the Workflows resource in the unified model. ### What authentication method does LinkSquares use? LinkSquares uses API key-based authentication. Truto manages token storage and refresh so your end users authenticate once through Truto's embedded linking flow. ### How does Truto handle pagination and rate limits for LinkSquares? Truto abstracts away provider-specific pagination and rate-limit handling. Your code calls the Unified API with standard cursor-based pagination while Truto manages retries and throttling against LinkSquares' endpoints.