Most teams evaluating a unified API ask about integration count and pricing. The questions that actually separate good infrastructure from expensive technical debt are different. Here's 10 questions your engineering team should ask any unified API vendor before you commit 👇

New in the Unified GenAI API: Task. A GenAI task is a cloud coding agent task. Two lookup objects came with it: GenAI Agent and GenAI Organization. New integrations: @AnthropicAI Agents, @codegen, @Cursor, @cognition Devin, @Google Jules, @github. Data model: docs.unified.to/genai/task/m…

Bank feed objects, live across 45 accounting, banking, and payment integrations. Two objects: Bankfeedaccount and Bankfeedtransaction. → Read the bank and card accounts a business has connected to its ledger. → Read the transactions that settle against them, in the same object model as the invoice. → Detect changes and deliver events on both. Including QuickBooks, Xero, NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, Odoo, Stripe, Brex, Ramp, Bill, and Pennylane. docs.unified.to/accounting/i…

New API category: Social Media. Read and write posts, profiles, reviews, and engagement metrics across social platforms through one category-scoped API. Supported integrations: Bluesky, Facebook, Google Business Profile, Instagram, LinkedIn, Mastodon, Pinterest, Threads, Trustpilot, and Twitter. Four objects: Profile, Post, Review, and Insight. → unified.to/social

Floats turns raw ATS data into client-ready candidate profiles for staffing agencies. Integrations weren't a feature for them, they were the entry ticket: if candidate data can't get out of the agency's ATS, there's no product. Building that layer in-house was most of a senior engineer-year, and every ATS they hadn't built yet was a deal they couldn't credibly pursue. They chose Unified.to for three reasons: extensive ATS coverage, scalable pricing, and candidate records not stored at rest. Floats now supports 140+ ATS platforms. A UK firm running Loxo was connected and pulling candidates within a week of the first onboarding call, six months after Floats had walked away from that same firm for lack of support. Read the full case study: unified.to/blog/how_floats_s…

In August, we launched a Social Media API and a Performance Management API, added bank feed objects across 45 accounting integrations, made payment terms a resolvable object rather than a string, expanded regional accounting, e-commerce, and POS coverage, and shipped 2,805 enhancements across the unified API. unified.to/blog/august_2026_…

We won the 2026 API Award for Best Innovation in Business Software API, presented at API:World last week. Big thanks to our team, and to the customers who put their integrations in our hands!

Unified's object count is lower by design. One call returns the record with its related data attached. Our models are designed for a category, so there are no integration-specific fields sitting inside them. A field means the same thing whether the source is NetSuite or Xero. Other unified APIs split that record across separate objects, so you assemble it yourself. That's an architecture decision that's locked in. Consolidating the objects would break every integration built against them. The outcome: more objects, more calls, more cost. Unified's models were built to grow: new categories, new fields, new sources, without breaking what you've already built against them. unified.to/technology

The AI-built integration was the easy part. Then you maintain it: tokens, rate limits, schema drift, monitoring. The opportunity cost is the product work that does not ship while engineering maintains integrations. Integrate with Unified instead → unified.to/

Enterprise software is being rebuilt around agents. Our CEO, @roymap, will be at @ElevateTechCA on September 23 discussing how LLMs are rewriting enterprise software. An open conversation on product strategy, defensibility, and where the real opportunities are for founders building now. Toronto, Sept 22–24. Come find us!

Our fintech catalogue keeps growing based on customer demand: 39 new accounting, e-commerce, and payments integrations shipped. Building a fintech product means reading across a lot of systems. Orders in one, settlements in another, ledger entries in a third. That's what our fintech cluster is built for: 232+ pre-built integrations across accounting, e-commerce, payments, and shipping. Most unified APIs return the invoice, its line items, and its payment allocations as separate objects, so you assemble the invoice yourself, four paginated calls per invoice. Unified returns it whole. And when the trail leads outside fintech, to a receipt in file storage or an approval in messaging, our category breadth has you covered.

New API category: Customer Data Platform Read customer profiles, segments, events, sources, destinations, and activations across CDP integrations through one category-scoped API. Supported integrations: Adobe Experience Platform, Amperity, Bloomreach Engagement (Exponea), BlueConic, Lytics, Rokt mParticle, Salesforce Data Cloud, Tealium, Treasure AI, and Twilio Segment. Six objects: Profile, Segment, Event, Source, Destination, and Activation. → unified.to/cdp

Breakthrough Jobs analyzes candidate data for hiring teams. Building integrations directly was too expensive and too slow, so they went to a unified API. Their first platform priced per linked account, which meant the bill grew with every connection each customer made. They switched to Unified for three reasons: pricing metered on API requests with customer connections unlimited, 126+ pre-built ATS integrations, and candidate records not stored at rest. Read the full case study: unified.to/blog/why_breakthr…

SAML SSO is live: Google Workspace Directory, JumpCloud, Microsoft Entra ID, and Okta supported at launch. Your enterprise customers' IT teams control who signs in to your product, and revoke it from their own directory. The offboarding that already happens there removes access to your application too. unified.to/login

July was a busy month: 1265 product enhancements. 108 new integrations. That product velocity is possible because of Unified's architecture. Reads pass through to the source, so there's no sync pipeline to build per integration. Authorization, change detection, and normalization happen once at the platform layer. Adding an integration means mapping a new source onto models that already exist. Breadth and depth stop competing for the same engineering resource. Full changelog: unified.to/changelog

In July, we added SAML SSO login, launched a Customer Data Platform API category, shipped Core Unified API mode for managing a workspace through MCP, added support for the stateless 2026-07-28 Model Context Protocol revision, and added 108 new integrations. We also won the 2026 API Award for Best Business Software API 🎉 unified.to/blog/july_2026_pr…

RAG on documents is easy. RAG on live SaaS data is where most pipelines break. When your source is a CRM, an ATS, or a ticketing system, the hard part isn't embedding. It's ingestion: detecting when a record changes, backfilling existing data, and keeping your index from serving a deal stage that already moved. How to Build a RAG Pipeline for Live SaaS Data with @Unified_api: unified.to/blog/how_to_build…

MCP v2 drops the session. Every request now stands on its own, which means MCP travels the same path as ordinary HTTP. It's in production on Unified.to, where you reach 43,456 tools across 577 integrations. The largest tool catalog available. Point your coding agent at it and it can search our API reference, get an answer back, create a connection, and read the API-call logs if something breaks. Docs: docs.unified.to/mcp/overview

MCP went stateless. The Unified MCP server now supports the 2026-07-28 revision in production. The initialize handshake and the protocol-level session are gone. Every request carries its own protocol version, client identity, and capabilities, and routing information now travels in HTTP headers, so a gateway can route an MCP call without reading the JSON-RPC body. No sessions, same server. Round-robin load balancing, no sticky routing, no shared session store. MCP now moves through the gateways and firewalls that used to drop it. With Unified, an agent inside a corporate network can reach the largest tool catalogue of any MCP server: 43,456 tools across 575 integrations. unified.to/blog/mcp_v2_is_he…

Why support 30 categories? Because our customers' use cases span them. Take recruiting. A product built on customer job data usually wants to advertise it too. The job lives in an ATS. The campaign lives on LinkedIn. ATS and Advertising is one pairing. The pattern repeats: CRM and Payments, Commerce and Shipping, HR and Verifications. Depth in one category is table stakes. Breadth across all of them is what lets you build the use case that spans your customer's systems. We wrote about how to do exactly this for one pairing, advertising jobs from any ATS: unified.to/blog/how_to_adver…