Integration Service user guide

DELIVERY:

Last updated Aug 13, 2025

Flex licensing

Note:

The information on this page applies to you if you are on Flex. If you are on Unified Pricing, refer to Unified Pricing licensing.

Integration Service licenses and entitlements

The following table provides a list of licenses that give you access to Integration Service, the plans associated with each license, and the entitlements enabled by them.

Table 1. Licensing plans
Feature	Community	Free	Pro	Enterprise
Access to connectors

Integration Service uses Service licenses, which can be distributed to your organizations and tenants. They target a specific metric, in this case, service consumption units, represented by Integration Service API calls.

Consumption unit

Integration Service uses API calls as a measure of consumption for executed Integration Activities. The consumption of API calls occurs in the following way: for every 1 executed activity, 5 API calls are used.

Table 2. Consumption rates based on process source
Process source	Consumption rate
API Workflows	1 activity = 5 API calls
Agents	1 activity = 5 API calls
Maestro	1 activity = 5 API calls
RPA Workflows (executed by attended, unattended, or serverless robots)¹	Not metered

¹ Integration Activities used in RPA Workflows, executed by attended, unattended, or serverless robots, are charged via the robot’s runtime licensing and are not metered separately.

An API call is consumed each time Integration Service makes a request to an external third-party application, whether initiated manually, via an attended automation, or through an unattended process. An executed activity may involve multiple API calls. For example, a single connector activity could call multiple endpoints or perform retries, and thus consume more than one API call.

Overconsumption

If you exceed your allocated monthly or annual API Call allocation:

There is no execution block mechanism enforced. Automations continue to run even after API call quotas are exceeded. There are currently no charges for overconsumed API calls.

License types

Integration Service API calls are made available to your organization in two main ways:

Bundled with License:

This pool represents the Integration Service API calls included with the user-based and robot-based licenses (e.g., Developer, Attended, Unattended, or Autopilot-related tiers) that your organization has subscribed to.

These API calls are allocated monthly and typically reset on the first day of each month. The number of calls included varies by license type and edition.
- Enterprise license: along with API Calls allocated for User and Bot, this pool includes the additional 100K API calls allocated from the Autopilot Express license.
- Pro and ProTrial licenses: along with API Calls allocated for User and Bot, this pool includes the additional 25K API calls allocated from the Autopilot Express license.
- Free license: The pool includes the 0-25K API calls allocated from the Autopilot Express license.
Dedicated API Call Bundles:

This pool represents the Platform SKU your organization has licensed. The API Calls allocated on your plan are from licensing one of the following Platform Individual SKUs:
- UiPath - Flex - Integration Service API Calls Bundle - 3M
- UiPath - Flex - Integration Service API Calls Bundle - 6M

Note: For details regarding all SKUs relevant to Integration Service, refer to the UiPath licensing platform.

Checking license allocation

To view organization-wide license distribution, log in to Automation Cloud^TM and go to Admin > Your Organization > Licenses.

The Licenses dashboard shows the number of all purchased licenses in your organization. You can switch to the Consumables tab to view license information for Integration Service.

API call prioritization logic

An API call is considered consumed whenever a request is made to an external third-party application via Integration Service. Consumption is calculated based on the total number of such requests, regardless of how they are initiated—whether triggered manually, through an attended automation, or via an unattended process.

The following example showcases how API call consumption is calculated and prioritized in a Flex licensing plan. It illustrates how organizations utilize their allocated API calls from both license-based bundles and additional API call bundles, and how the usage affects future availability based on monthly consumption.

If both bundled and dedicated bundles are available:

Consumption first draws from the monthly bundled license pool.
Once depleted, usage continues from the dedicated bundle.

Example:

Your org holds:
- 10 Automation Developer licenses (10 × 5,000 = 50,000 API calls)
- 10 Unattended Robot licenses (10 × 5,000 = 50,000 API calls)
- 3M API call bundle (annual)

Monthly total: 100,000 bundled calls.

In October 2023, 125,000 calls were used: