# API workflows licensing

> Consumption of Platform Units and API calls by API workflow executions under Unified Pricing and Flex.

API workflows are licensed per **workflow execution**. Integration Service usage inside the workflow — connector activities, HTTP Request activities, and Integration Service triggers — is included and not metered.

## What is and isn't metered

API workflow execution is a standalone charge, separate from Integration Service.

Table 1. Billable — workflow execution

| Item | Unified Pricing | Flex |
| --- | --- | --- |
| API workflow execution | 0.05 Platform Units per execution | 15 API calls per execution |

The execution of an API workflow is charged as a fixed, flat fee. The Integration Service activities executed as part of the workflow are included and are not charged.

Table 2. Included — Integration Service usage

| Item | Metering |
| --- | --- |
| Integration Service trigger | Not metered — included |
| HTTP Request activity | Not metered — included |
| Connector activity | Not metered — included |
| Script and control flow activities (for example, If, Loop, or Try/Catch) | Not metered — included |
| Calls to UiPath platform services through a Platform Connector (for example, Orchestrator or Data Fabric) | Not metered — included |

For Integration Service licensing details, refer to [Integration Service licensing overview](https://docs.uipath.com/integration-service/automation-cloud/latest/user-guide/integration-service-licensing-overview).

### Example

An API workflow that runs manually once and makes two HTTP Request calls and one connector call is billed only for the workflow execution — 0.05 Platform Units or 15 API calls. The HTTP Request and connector activities are Integration Service usage and are included.

If an Integration Service trigger starts the same workflow instead of a manual run, the charge is unchanged. Only the workflow execution is billed.

## Known limitation: delayed consumption reporting

Execution consumption is reported on a delayed batch cycle of approximately one hour. Because of this delay, the Consumption field was removed from the Orchestrator job details page in [July 2026](https://docs.uipath.com/orchestrator/automation-cloud/latest/release-notes/july-2026#consumption-field-hidden-from-job-details) until real-time reporting is available.

:::note
To check consumption totals, go to **Admin \> Your Organization \> Licenses \> Consumables**. This view shows aggregate totals for your organization or tenant, not a per-job breakdown.
:::