API workflows licensing

Consumption of Platform Units and API Calls by API workflow jobs, triggers, and activities under Unified Pricing and Flex.

How consumption is measured

API workflows are licensed through the consumption of Integration Activities. Every execution of an API workflow consumes one Integration Activity for the job itself. Chargeable activities and the trigger that starts the job consume additional Integration Activities.

Table 1. Consumption items for API workflows

Elément	Integration Activities consumed	Tarification unifiée	Flex
Workflow start (manual execution or event trigger)	1 per run	0.02 Platform Units per run	5 API Calls per run
Integration Service trigger	1 each time the trigger successfully starts the job	0.02 Platform Units per successful start	5 API Calls per successful start
Activité de requête HTTP	1 per request sent to an external system	0.02 Platform Units per request	5 API Calls per request
Activités du connecteur	1 per successful connector execution	0.02 Platform Units per successful execution	5 API Calls per successful execution
Script and Control Flow activities (for example, If, Loop, or Try/Catch)	0	0 Platform Units	0 API Calls
Calls to UiPath platform services through a Platform Connector (for example, Orchestrator or Data Fabric)	0	0 Platform Units	0 API Calls

There is no separate execution or runtime charge for API workflows beyond the Integration Activities listed above. One Integration Activity equals 5 API Calls under Flex, or 0.02 Platform Units under Unified Pricing. For the full consumption rate tables, license allotments, and SKUs, see:

• Integration Service licensing overview
• Licences à tarification unifiée
• Licences Flex

Exemple

An API workflow that runs manually once and makes two HTTP Request calls consumes 3 Integration Activities in total: 1 for the job execution and 1 for each HTTP Request activity. Under Flex, this equals 15 API Calls. Under Unified Pricing, this equals 0.06 Platform Units.

If an Integration Service trigger starts the same workflow, the trigger consumes one additional Integration Activity. The triggered run consumes 4 Integration Activities in total, equal to 20 API Calls under Flex or 0.08 Platform Units under Unified Pricing.

Known limitation: delayed consumption reporting

Integration Service reports activity consumption 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 until real-time reporting is available.

Remarque :

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. Use Table 1 to calculate the consumption of an individual API workflow execution.