--- title: Truto API Integration on Truto slug: truto category: Default canonical: "https://truto.one/integrations/detail/truto/" --- # Truto API Integration on Truto **Category:** Default **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 - [Kombo vs Finch vs Truto: Which Unified API Architecture Wins in 2026?](https://truto.one/blog/kombo-vs-finch-vs-truto-which-unified-api-architecture-wins-in-2026/) — Evaluating Kombo, Finch, and Truto for your B2B SaaS integrations? Discover which unified API architecture scales best across HRIS, Payroll, CRM, and beyond. - [Boomi vs Tray.io vs Merge vs Truto: 2026 Integration Architecture Guide](https://truto.one/blog/boomi-vs-trayio-vs-merge-vs-truto-2026-integration-architecture-guide/) — Compare Boomi, Tray.io, Merge.dev, and Truto across architecture, pricing, data residency, and scalability. A technical guide for B2B SaaS teams in 2026. - [StackOne vs Composio vs Truto: AI Agent Integration Benchmarks (2026)](https://truto.one/blog/stackone-vs-composio-vs-truto-ai-agent-integration-benchmarks/) — Compare Composio, StackOne, and Truto for connecting LangChain and LlamaIndex agents to external SaaS data. Covers OAuth, pagination, rate limits, MCP support, and per-use-case recommendations. - [Introducing the Truto CLI](https://truto.one/blog/introducing-truto-cli/) — Manage your entire Truto integration platform from the terminal. Install in one command, query unified APIs, export data, batch operations, and diff records. - [How to Create an Apideck-to-Truto Migration Guide (Without Re-Authenticating Users)](https://truto.one/blog/how-to-create-an-apideck-to-truto-migration-guide-without-re-authenticating-users/) — Learn how to migrate from Apideck to Truto without forcing users to re-authenticate. Covers OAuth app ownership checks, Apideck Vault token export, credential import, schema mapping, smoke tests, and rollback procedures. - [Kombo vs Finch vs Truto: Why Single-Vertical Unified APIs Hit a Wall](https://truto.one/blog/kombo-vs-finch-vs-truto-why-single-vertical-unified-apis-hit-a-wall/) — Comparing Kombo and Finch for HRIS and payroll integrations, and why growing B2B SaaS companies are migrating to multi-category unified APIs like Truto to scale.