--- title: Akoya API Integration on Truto slug: akoya category: Accounting canonical: "https://truto.one/integrations/detail/akoya/" --- # Akoya API Integration on Truto **Category:** Accounting **Status:** Generally available ## Unified APIs ### Unified Finance API - **Accounts** — ## How it works 1. **Link your customer's Akoya 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 Akoya.** The Proxy API is a 1-to-1 mapping of the Akoya 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 bank feed syncing for cloud accounting platforms** — Accounting and ERP platforms can offer native bank feed connections so business users stop uploading CSVs. By integrating Akoya through Truto, your users link their corporate bank accounts via OAuth and get daily transaction data pulled automatically for ledger reconciliation. - **Real-time balance checks for spend management and treasury tools** — Spend management platforms issuing corporate cards or automating vendor payouts need to verify available funds before executing large payment runs. Akoya's direct API connections to major banks provide reliable, real-time balance data to prevent overdrafts and failed payments. - **Streamline cash-flow underwriting for B2B lending platforms** — Lending and credit underwriting SaaS products can let applicants securely connect their bank accounts to pull up to 24 months of standardized transaction history. This eliminates manual document collection and powers automated cash-flow analysis for faster credit decisions. - **Instant account verification for B2B payment enablement** — Payment platforms can replace slow micro-deposit verification by pulling routing and account numbers directly through Akoya's payments endpoint. This dramatically speeds up ACH and RTP vendor payment setup for your business users. - **Automated KYC/KYB identity verification during onboarding** — SaaS platforms with compliance requirements can pull bank-verified customer identity data — name, email, address — directly from financial institutions to streamline know-your-customer and know-your-business checks without manual document uploads. ## What you can build - **Automated nightly bank transaction sync** — Pull the previous day's cleared transactions from connected corporate bank accounts on a scheduled basis to auto-reconcile your users' ledgers without manual intervention. - **Pre-payment liquidity verification** — Query real-time available balances across checking, savings, and credit accounts before executing payment runs to reduce failed transaction fees. - **One-click bank account linking via OAuth** — Let your end users securely connect their accounts at major institutions like Chase, Wells Fargo, and Bank of America through a bank-hosted OAuth flow — no credential sharing or screen scraping involved. - **Instant ACH/RTP account verification** — Retrieve verified routing and account numbers directly from the financial institution to set up vendor payments instantly, eliminating the multi-day micro-deposit process. - **Automated bank statement collection for audit compliance** — Pull official monthly bank statements in PDF format from connected accounts to satisfy audit, underwriting, or regulatory document requirements without chasing users for uploads. - **Bank-verified identity enrichment** — Populate your onboarding forms with verified customer name, email, and address data sourced directly from the user's financial institution for seamless KYC/KYB checks. ## FAQs ### How does authentication work with Akoya? Akoya uses a redirect-based OAuth flow where the end user authenticates directly with their bank's portal and grants consent for specific accounts. Uniquely, Akoya requires the OAuth id_token (not a standard access token) to be passed as the Bearer token in API calls. Truto handles this non-standard auth pattern, including aggressive token refreshing since bank tokens typically expire in as little as 15 minutes. ### Does Akoya store my users' financial data? No. Akoya acts as a secure pass-through network. It does not store end-user financial data. All data flows directly from the financial institution through Akoya's API to your application using tokenized access. ### What data format does Akoya return? Akoya standardizes all responses into the FDX (Financial Data Exchange) format. API calls use a `?mode=standard` parameter to ensure consistent, FDX-aligned payloads regardless of which bank is connected, eliminating the need to map bank-specific schemas yourself. ### Which financial institutions does Akoya support? Akoya connects to a growing network of major North American financial institutions including Chase, Wells Fargo, Bank of America, Fidelity, and Citi, all via direct 100% API integrations with no screen scraping. ### What is the difference between interactive and batch requests? Akoya requires an `x-akoya-interaction-type` header set to either `USER` (when the end user is actively in your app, e.g., refreshing a dashboard) or `BATCH` (for background jobs like nightly transaction syncs). Truto can manage this header dynamically based on the request context. ### Are Truto's Unified API tools available for Akoya today? Akoya is supported under Truto's Unified Finance API for Accounts. Specific tools and resource mappings are built on request to match your use case. Contact Truto to scope your integration and get up and running quickly.