API changes in Ansible Automation Platform 2.7
Ansible Automation Platform 2.7 completes the migration of all API access to platform gateway. Direct API access to individual services that was deprecated in versions 2.5 and 2.6 has been removed in this release.
These changes impact your organization if you have API calls, scripts, or integrations that connect directly to automation controller, automation hub, or Event-Driven Ansible hosts. All API requests must now use platform gateway endpoints. Requests sent directly to component hosts return an HTTP 401 Unauthorized error.
This section highlights the changed APIs between 2.6 and 2.7.
General API changes Copy linkLink copied!
In Ansible Automation Platform 2.7, direct API access to individual platform components has been removed. All API access must go through platform gateway.
Service-specific API endpoints have been removed in Ansible Automation Platform 2.7. Direct component API access is no longer available. All API access must go through platform gateway.
| Component | 2.4 and earlier endpoints start with... | 2.5 and 2.6 endpoints start with... | 2.7 endpoints start with... |
|---|---|---|---|
| Automation controller | /api/v2/ |
/api/controller/v2/ |
Must use platform gateway: /api/controller/v2/ |
| Automation hub | /api/automation-hub |
/api/galaxy/v1 |
Must use platform gateway: /api/galaxy/v1 |
| Platform gateway | Not applicable | /api/gateway/v1/ |
/api/gateway/v1/ |
| Event-Driven Ansible | Not applicable | /api/eda/v1/ |
Must use platform gateway: /api/eda/v1/ |
In Red Hat Ansible Automation Platform 2.7, these API endpoints are only accessible through the platform gateway hostname. Direct access to component hostnames (such as controller.example.com or hub.example.com) returns an HTTP 401 Unauthorized error.
Example:
- Works in 2.7:
https://gateway.example.com/api/controller/v2/ping/ - Blocked in 2.7:
https://controller.example.com/api/v2/ping/
Specific API changes Copy linkLink copied!
In Red Hat Ansible Automation Platform 2.7, all API access must go through the platform gateway hostname. Direct access to component hostnames has been removed.
| Old (Ansible Automation Platform 2.6) | New (Ansible Automation Platform 2.7) | Status |
|---|---|---|
https://controller.example.com/api/v2/* |
https://gateway.example.com/api/controller/v2/* |
Required |
https://hub.example.com/api/automation-hub/* |
https://gateway.example.com/api/galaxy/* |
Required |
https://eda.example.com/api/eda/v1/* |
https://gateway.example.com/api/eda/v1/* |
Required |
Attempting to access component hostnames directly (controller.example.com, hub.example.com, eda.example.com) returns HTTP 401 Unauthorized in Red Hat Ansible Automation Platform 2.7.