What is a Unified API?

Updated:

For how unified APIs differ and how to choose a vendor, see What Is a Unified API? on the blog.

A unified API is a single API interface that aggregates multiple third-party APIs in the same software category (CRM, accounting, HRIS, ATS, payroll, and others) behind one standardized endpoint. With a unified API, applications authenticate once, integrate once, and receive normalized data from any supported integration in that category.

This page is the technical concept reference for how Unified.to implements that idea. The definition, the architecture trade-offs (pass-through vs. sync-based), pricing models, and guidance on when a unified API is or isn't the right choice are covered in the blog guide and in Pass-through vs. sync-based unified APIs.

What complexity does a unified API remove?

A unified API removes per-vendor variance in four specific areas:

  • Authentication and authorization: different OAuth2 flows, API key schemes, scope models, and token refresh behaviours collapse into a single authentication interface.
  • Data representation: different schemas, field names, and data types collapse into a normalized data model per category.
  • Endpoint structure: different URL patterns, HTTP methods, and request formats collapse into consistent endpoints across the category.
  • Error handling: different error codes, response formats, and rate-limit behaviours collapse into consistent error semantics.

What a unified API does not remove is the underlying difference in vendor capability. If one vendor in a category supports a feature that others do not, the unified API still has to choose how to surface it, typically through raw fields or the Metadata API (see custom fields and custom objects).

How are unified API endpoints structured?

A unified API has the same endpoints for each integration category. An API call to retrieve CRM contacts is identical regardless of which underlying CRM provides the data. Endpoints are RESTful and consistent across all integrations in the category. See the REST reference.

How does data normalization work across vendors?

Data models are unified, not just endpoints. A CRM contact returned from one vendor has the same field structure as a CRM contact returned from another. Two depth dimensions determine how useful a normalized model is:

  • Field coverage: how many fields per object are normalized into the unified schema.
  • Object coverage: how many distinct object types per category are supported (for CRM: contacts, companies, deals, pipelines, activities, notes, and so on).

Each integration's Feature Support tab shows which objects and fields it supports.

How is authentication handled?

Unified.to provides a single authentication flow across all integrations. Common authentication metadata (vendor name, account name, scopes granted) is available programmatically so your application can display connection state natively.

A pre-built authorization component handles the OAuth2 handshake with end users, reducing your authentication work to a single integration. See Embedded components.

How are permission scopes managed?

Along with unified authentication, Unified.to provides abstracted permission scopes so you don't need to research per-vendor OAuth2 scopes for each use case. Scope abstraction maps your application's intent (for example, "read contacts") to the appropriate per-vendor scopes. See Scopes.

How do unified APIs handle vendors that don't support webhooks?

Most SaaS APIs do not support native webhooks. Unified.to delivers events through virtual webhooks regardless of whether the vendor supports webhooks natively.

  • The check interval is a setting you choose.
  • Events carry the changed records on supported integrations, so you don't need a second request to fetch them.
  • Checks that find no changes aren't billed.

From your application's perspective, native and virtual webhooks use the same subscription model and event format. See Webhooks for the event reference.

How are custom fields and custom objects handled?

Normalizing across many vendors can lose vendor-specific features, custom fields, and custom objects. Unified.to handles this with:

  • Custom fields: vendor custom fields are returned in the unified object's metadata array where the integration supports it, and described programmatically by the Metadata API.
  • Custom objects: read vendor-specific data and custom objects with fields=raw, and write vendor-specific values with raw. See Choosing how to access vendor-specific data.
  • Passthrough: call vendor endpoints that aren't part of the unified model, using your existing connection's authentication. See Passthrough.

Unified.to

Unified.to is a unified API across CRM, accounting, HRIS, ATS, payroll, ticketing, e-commerce, messaging, and many other categories. For the current list of integrations and categories, see the integrations directory.

Unified.to also provides a hosted MCP (Model Context Protocol) server that lets AI agents read and write across customer SaaS integrations through a single connection-scoped interface. See MCP and the MCP changelog for the current tool catalogue. Each connection sees only the tools for its own integration, not the full catalogue.

How Unified.to handles your customers' data

Unified.to doesn't store your customers' records. When you make an API request, Unified.to fetches only the data you asked for from the vendor, processes it in memory, and discards it when the request completes.

What Unified.to stores:

  • Connection records
  • Connection credentials, encrypted
  • Operational metadata, encrypted
  • API call logs, which never include payloads. See How long are logs retained.

Shared responsibilities

You're responsible for:

  • Registering OAuth applications with each vendor and providing the credentials when you activate integrations
  • Integrating your application with the Unified API, through an SDK or REST
  • How you store and handle customer data, including personal information, in your systems

Unified.to is responsible for:

  • Maintaining integrations as vendor APIs change
  • OAuth flows and token management
  • The stability, scalability, and uptime of the Unified API

SLAs

Unified.to doesn't currently offer a formal SLA on the API or webhooks. Custom agreements can include uptime or error-rate guarantees on a case-by-case basis.

For pricing details, see unified.to/pricing. For full API documentation, see docs.unified.to.

Are we missing anything? Let us know
Was this page helpful?