Start testing for free or pay per use with unrestricted access.


Get 30 days of unlimited access to test our unified APIs in non-production applications. No credit card needed.


Get started


For launching unified APIs in production applications.


Get started


For production applications with growing customer usage.


Get started


For large-scale applications with high customer usage.


Get started


Contact us for custom limits, pricing, and configurations.

Speak to an expert

Pricing calculator

You have customers.

Each customer has connection on average.

Each connection has API requests per day on average.

On average, you will have 100 customer connections with 74,400 total API request per month.

You should get the Startup plan for only $372/month ($3.72/customer/month). That is 22x less expensive than 1 developer!

Get started with the Startup plan

Pricing FAQ

What is an API request?

An API request represents interactions between Unified.to and a third-party system on behalf of your customers. API requests occur when your app calls Unified.to to fetch data, when Unified.to's webhook calls a third-party system, or when a third-party system sends Unified.to a webhook.

Consider the valuable customer data you require to enhance user experience — whether it's a new contact, an updated CRM deal, or a change in job application status. Every time you request data from an integration through Unified.to, it counts as an API request.

For example, requesting "List Employees" and receiving up to 100 employee records counts as one API request. Requesting the next page of 100 employees is a second API request.

Our transparent usage-based pricing model calculates the total number of API requests across all your integrations every month. You can choose to subscribe to a monthly or annual plan.

How does usage-based pricing work?

Our pricing is based on the number of API requests you make each month. This model allows you to start small and confidently scale your integrations as your usage grows with volume discounts. If you happen to exceed the number of API requests included in your plan, we’ll calculate any additional requests you’ve made and adjust your bill accordingly, in line with your chosen plan.

You can upgrade your plan whenever you like. If you're interested in a custom option, please reach out to our sales team.

What is a customer connection?

A customer connection refers to a third-party account that has been authorized by your customer through Unified.to to be linked with your app. In some platforms, a customer connection is called a linked account. Customers can have multiple connections, allowing them to authorize various third-party accounts. For example, if a customer authorizes Greenhouse, HubSpot, and Google Drive, this results in three customer connections.

Your customers can only authorize third-party accounts from integrations that you have activated in Unified.to. Each of our paid plans includes unlimited customer connections.

What is an integration?

An integration refers to a seamless link between your app and your customer's third-party account. Unified.to builds and maintains integrations, so you don't have to. Our integrations are pre-configured and ready to use, allowing your app to interact with your customers' third-party accounts, access their data, or perform specific actions without extensive custom development work.

For example, when you integrate with Salesforce, you can access your customers' CRM data in real-time, including Event, Deal, and Lead information.

You can push and pull data within your customers' third-party accounts through our integrations. Each of our plans has unlimited integrations.

What is an integration category?

An "integration category" or "API category" refers to a classification of APIs, including API endpoints, data models, webhooks, and more, organized based on the type of software system they connect to and the supported objects they handle.

For instance, our CRM category includes integrations with CRM systems like Salesforce, HubSpot, and ActiveCampaign, handling objects such as Contacts, Deals, and Companies.

Some of our integrations may belong to multiple categories. For example, our HR category spans multiple software types, enabling users to exchange employee data with various third-party accounts, such as Zoom, Notion, and Zendesk.

When you activate an integration within the Unified.to dashboard, you'll have the option to specify the category you want to enable. This categorization ensures that you request access only to the data relevant to your needs.

What is a webhook?

A webhook is an automated way for software systems to communicate and share real-time data.

A native webhook is directly built into or provided by a software system. A native webhook occurs when a third-party system sends requested data to Unified.to. To receive this updated data, you need to subscribe to a Unified.to webhook and specify a hook URL for the data transmission.

However, not every third-party system has its own native webhook. That’s why Unified.to created virtual webhooks to mimic webhook behavior by regularly polling and sending data back to your hook URL.

Each plan includes unlimited webhook subscriptions. However, please note that the events triggered by webhook usage count towards your plan's monthly API request limit. Billable events for virtual webhooks include attempts to read data or dispatch those results to you (but not both simultaneously). Non-billable events include encountering an error when reading data from an integration.

What are OAuth 2 credentials?

OAuth 2 is a widely accepted protocol that provides a secure and convenient way to access a user's data without the need to share their personal credentials like email or password.

Many third-party systems rely on OAuth 2 to grant access to your customer's data. To start using an integration that supports OAuth 2 within Unified.to, you'll first need to register your app with the third-party system to get your OAuth 2 credentials, which include a client ID.

For testing purposes, you can use Unified.to's OAuth 2 credentials for some of our integrations. However, when you're ready to go live, it's important to switch to your app's OAuth 2 credentials. This ensures that your customers will see your branding during the authorization process.

For more detailed instructions on obtaining OAuth 2 credentials for various third-party systems, check out our comprehensive guides.

What support do you offer?

Our support services vary depending on your plan. We provide extensive assistance for all users through our comprehensive API documentation, developer guides, Discord, and video tutorials. Our paid plans include dedicated Slack/Discord channels, onboarding calls, and direct access to our engineers.

While we value feedback from all users, we prioritize feature requests from those on paid plans. Our support team operates Monday to Thursday from 9:00 am to 5:00 pm ET, with limited live chat support on Friday.

For teams requiring SLAs, we offer custom support through our Enterprise Plan. Contact us to learn more.

What is the CNAME (Custom Auth Domain) feature?

On all Unified.to plans, we offer a white-labelled UI, allowing the authorization page visited by your end-users for API-key based integrations to display your brand. For Growth and Scale plans, you can also set a custom domain, replacing the default auth.unified.domain. This feature enhances brand consistency by ensuring your users see your domain during the authorization process. Please note: the Auth CNAME feature is currently only available for API-key based integrations, with plans to extend this to OAuth 2 integrations in the near future.