--- title: Truto API Integration on Truto slug: truto category: Application Development canonical: "https://truto.one/integrations/detail/truto/" --- # Truto API Integration on Truto **Category:** Application Development **Status:** Generally available ## How it works 1. **Link your customer's Truto 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 Truto.** The Proxy API is a 1-to-1 mapping of the Truto 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 - **Accelerate enterprise deal closure with native integrations** — Enterprise prospects frequently require integrations with their existing tool stack before signing. SaaS companies can use Truto to rapidly expand their integration catalog without dedicating engineering sprints to each new connector, unblocking sales cycles. - **Power AI agents with real-time SaaS context** — Companies building AI copilots or autonomous agents need authenticated read/write access to their end users' CRM, ticketing, or HRIS systems. Truto's MCP Server capability lets LLM-based agents dynamically discover and invoke SaaS tools without custom adapter code. - **Offload OAuth and token lifecycle management** — Managing OAuth flows, token refreshes, and credential storage across dozens of third-party APIs is a persistent engineering burden. SaaS teams use Truto to fully delegate authentication plumbing so they can focus on product logic instead of auth edge cases. - **Simplify compliance with zero-data-retention architecture** — B2B SaaS companies handling sensitive customer data face SOC 2, GDPR, and HIPAA scrutiny on every integration. Truto's pass-through architecture normalizes payloads in memory without persisting end-user data, reducing the compliance surface area of offering third-party integrations. - **Let end users selectively control what data flows into your product** — For integrations involving large or sensitive datasets, SaaS companies can use Truto's RapidForm to present end users with granular data-selection controls—like choosing specific pages, projects, or accounts to sync—rather than ingesting everything by default. ## What you can build - **Embeddable account linking flow** — Ship a polished 'Connect your tools' experience using Truto's Frontend SDK, where end users authenticate their SaaS accounts via OAuth without your team managing any handshake or token refresh logic. - **AI copilot with live SaaS tool access** — Route your LLM agent's function calls through Truto's MCP Server endpoints so the agent can dynamically read, create, and update records across your users' connected apps in real time. - **Normalized webhook event pipeline** — Receive clean, standardized webhook events from connected third-party apps—with provider-specific security validation handled automatically—so your application reacts to changes like new records or status updates without parsing raw provider payloads. - **Proxy API escape hatch for deep provider features** — When your product needs provider-specific functionality that goes beyond a unified model, use Truto's Proxy API to make raw, authenticated calls to any connected app without managing credentials yourself. - **Selective data sync with end-user control** — Leverage RapidForm and RapidBridge to let end users choose exactly which resources to sync and stream normalized records directly into your database for analytics or RAG pipelines. - **Custom field mapping via JSONata overrides** — Allow your platform to dynamically map tenant-specific custom fields from connected apps into your internal data models using Truto's Override Hierarchy, without writing new adapter code per customer. ## FAQs ### How does Truto handle authentication for connected accounts? Truto fully manages the OAuth handshake, securely stores credentials, and proactively refreshes access tokens—including providers with aggressive expiration windows. Your application never touches raw tokens. ### Does Truto store my end users' data? No. Truto uses a pass-through architecture that normalizes API responses in memory and forwards them directly to your application. No end-user data is persisted on Truto's infrastructure, which simplifies SOC 2, GDPR, and HIPAA compliance. ### What happens when I need provider-specific functionality not covered by a unified model? You can use the Proxy API to make raw, authenticated API calls directly to the underlying provider. Truto still manages the auth context and credentials—you just send the request as if you were calling the provider's API natively. ### How does Truto handle pagination and rate limits across different providers? Truto normalizes all provider-specific pagination formats into a single cursor-based pagination model. It also manages rate-limit detection and retry logic behind the scenes, so your application receives consistent, predictable API behavior regardless of the provider. ### Are specific Unified APIs and tools available for Truto today? Truto integrations are built on request. When you need a specific integration or unified model, Truto's team scopes and delivers it. Contact the Truto team to discuss your requirements and timeline. ### How does the MCP Server integration work for AI agents? Truto exposes connected accounts as MCP (Model Context Protocol) Servers. Your AI agent framework—LangChain, Claude, or others—can dynamically discover available tools and execute authenticated API calls through Truto without you writing custom agent schemas or tool definitions. ## Related reading - [Workato Embedded vs Merge vs Truto: The 2026 Interactive Architecture Comparison](https://truto.one/blog/workato-embedded-vs-merge-vs-truto-the-2026-interactive-architecture-comparison/) — A deep-dive architectural comparison of Workato Embedded, Merge.dev, and Truto for B2B SaaS teams evaluating iPaaS vs unified API infrastructure. - [MuleSoft vs Workato vs Merge vs Truto: 2026 Architecture & Feature Matrix](https://truto.one/blog/mulesoft-vs-workato-vs-merge-vs-truto-2026-architecture-feature-matrix/) — A highly technical 2026 architecture comparison of MuleSoft, Workato, Merge.dev, and Truto. Discover which integration paradigm fits your B2B SaaS. - [Does Truto Support QuickBooks and Xero Integration? (2026 Architecture Guide)](https://truto.one/blog/does-truto-support-quickbooks-and-xero-integration-2026-guide/) — Evaluate how Truto's Unified Accounting API normalizes QuickBooks and Xero schemas, handles rate limits, and enables zero data retention integrations. - [Does Truto Support White-Labeled OAuth for Calendar Apps?](https://truto.one/blog/does-truto-support-white-labeled-oauth-for-calendar-apps/) — Yes, Truto supports fully white-labeled OAuth for Google and Microsoft calendar integrations. Learn how our 3-level credential hierarchy and proactive token refresh works. - [Unified.to vs Apideck vs Truto: Best Unified API for CRM & Ticketing](https://truto.one/blog/unifiedto-vs-apideck-vs-truto-best-unified-api-for-crm-ticketing/) — A technical comparison of Unified.to, Apideck, and Truto for CRM and ticketing integrations. Evaluate pricing, custom fields, and real-time pass-through APIs. - [Merge.dev vs Truto: The 2026 Migration & Performance Playbook](https://truto.one/blog/mergedev-vs-truto-the-2026-migration-performance-playbook/) — A technical playbook for evaluating Merge.dev alternatives and executing a zero-downtime migration - OAuth tokens, schema mapping, and rollback plans.