Feature availability across Automation Hub delivery options, listing capabilities that differ between Automation Cloud and Automation Cloud Public Sector.

The following tables list features and their availability across delivery options.

The following table lists features that are not available across all cloud platforms.

The following pages have structural differences between Automation Cloud and Automation Cloud Public Sector that go beyond feature availability. They are documented separately for each platform.

The API base URL differs by deployment environment. Automation Cloud uses https://<accessURL>/{orgName}/{tenantName}/automationhub_/api/v1/openapi, while Automation Cloud Public Sector uses https://govcloud.uipath.us/api/v1/openapi — the path structure itself differs, not just the domain. Automation Cloud Public Sector also provides a separate Delayed Release URL (http://ah-gxp-openapi-us.uipath.com/api/v1/openapi/), which has no equivalent in Automation Cloud. Additionally, the API References content is embedded directly in the Introduction page for Automation Cloud, and available as a dedicated page for Automation Cloud Public Sector.

The authentication setup procedure differs by platform. Automation Cloud describes the Bearer token structure and provides an example GET request to the authinfo endpoint to retrieve token details. Automation Cloud Public Sector describes generating the API token from the Open API page in the Automation Hub UI and additionally documents an optional App Key header (x-ah-openapi-app-key) that is not mentioned in the Automation Cloud documentation.