How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Red Hat Ansible Automation Platform Inventory Sources API

The inventory_sources API from Red Hat Ansible Automation Platform — 12 operation(s) for inventory_sources.

Red Hat Ansible Automation Platform Inventory Sources API is one of 333 APIs that Red Hat Ansible Automation Platform publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Inventory Sources. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 24 operations across 12 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against the base URL https://controller-host/api/v2/.

24 operations 12 paths 22 schemas 3 DELETE12 GET1 PATCH7 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://controller-host/api/v2/
License
Apache License
Resource Areas
1

Paths & Operations 24

Across 12 paths, the API surfaces 24 operations — 3 DELETE, 12 GET, 1 PATCH, 7 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Inventory Sources 24
GET
/api/v2/inventory_sources/
Inventory sources list
inventory_sources_list 7 params → 200
POST
/api/v2/inventory_sources/
Inventory sources create
inventory_sources_create body → 201
GET
/api/v2/inventory_sources/{id}/
Inventory sources retrieve
inventory_sources_retrieve 1 param → 200
PUT
/api/v2/inventory_sources/{id}/
Inventory sources update
inventory_sources_update 1 param body → 200
PATCH
/api/v2/inventory_sources/{id}/
Inventory sources partial update
inventory_sources_partial_update 1 param body → 200
DELETE
/api/v2/inventory_sources/{id}/
Inventory sources destroy
inventory_sources_destroy 1 param → 204
GET
/api/v2/inventory_sources/{id}/activity_stream/
Inventory sources activity stream list
inventory_sources_activity_stream_list 8 params → 200
GET
/api/v2/inventory_sources/{id}/credentials/
Inventory sources credentials list
inventory_sources_credentials_list 8 params → 200
POST
/api/v2/inventory_sources/{id}/credentials/
Inventory sources credentials create
inventory_sources_credentials_create 1 param body → 201
GET
/api/v2/inventory_sources/{id}/groups/
Inventory sources groups list
inventory_sources_groups_list 8 params → 200
DELETE
/api/v2/inventory_sources/{id}/groups/
Inventory sources groups destroy
inventory_sources_groups_destroy 1 param → 204
GET
/api/v2/inventory_sources/{id}/hosts/
Inventory sources hosts list
inventory_sources_hosts_list 8 params → 200
DELETE
/api/v2/inventory_sources/{id}/hosts/
Inventory sources hosts destroy
inventory_sources_hosts_destroy 1 param → 204
GET
/api/v2/inventory_sources/{id}/inventory_updates/
Inventory sources inventory updates list
inventory_sources_inventory_updates_list 8 params → 200
GET
/api/v2/inventory_sources/{id}/notification_templates_error/
Inventory sources notification templates error list
inventory_sources_notification_templates_error_list 8 params → 200
POST
/api/v2/inventory_sources/{id}/notification_templates_error/
Inventory sources notification templates error create
inventory_sources_notification_templates_error_create 1 param body → 201
GET
/api/v2/inventory_sources/{id}/notification_templates_started/
Inventory sources notification templates started list
inventory_sources_notification_templates_started_list 8 params → 200
POST
/api/v2/inventory_sources/{id}/notification_templates_started/
Inventory sources notification templates started create
inventory_sources_notification_templates_started_create 1 param body → 201
GET
/api/v2/inventory_sources/{id}/notification_templates_success/
Inventory sources notification templates success list
inventory_sources_notification_templates_success_list 8 params → 200
POST
/api/v2/inventory_sources/{id}/notification_templates_success/
Inventory sources notification templates success create
inventory_sources_notification_templates_success_create 1 param body → 201
GET
/api/v2/inventory_sources/{id}/schedules/
Inventory sources schedules list
inventory_sources_schedules_list 8 params → 200
POST
/api/v2/inventory_sources/{id}/schedules/
Inventory sources schedules create
inventory_sources_schedules_create 1 param body → 201
GET
/api/v2/inventory_sources/{id}/update/
Inventory sources update retrieve
inventory_sources_update_retrieve 1 param → 200
POST
/api/v2/inventory_sources/{id}/update/
Inventory sources update create
inventory_sources_update_create 1 param → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are InventoryUpdateList (44 properties), InventorySource (34 properties), Schedule (30 properties), InventorySourceRequest (20 properties). Each schema is shown below with its type and property counts.

Schedule
object
30 properties 3 required
Host
object
18 properties 2 required
NotificationTemplateRequest
object
6 properties 3 required
ActivityStream
object
13 properties 3 required
PaginatedInventorySourceList
object
4 properties 2 required
Group
object
11 properties 2 required
PaginatedScheduleList
object
4 properties 2 required
CredentialRequest
object
5 properties 2 required
PaginatedInventoryUpdateListList
object
4 properties 2 required
PaginatedHostList
object
4 properties 2 required
InventorySourceRequest
object
20 properties 3 required
Credential
object
16 properties 2 required
InventorySourceUpdate
object
1 property
PaginatedNotificationTemplateList
object
4 properties 2 required
PatchedInventorySourceRequest
object
20 properties
PaginatedActivityStreamList
object
4 properties 2 required
PaginatedCredentialList
object
4 properties 2 required
InventorySource
object
34 properties 3 required
ScheduleRequest
object
18 properties 3 required
NotificationTemplate
object
13 properties 3 required
InventoryUpdateList
object
44 properties 2 required
PaginatedGroupList
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

red-hat-ansible-automation-platform-inventory-sources-api-openapi.yml Raw ↑

Other APIs Red Hat Ansible Automation Platform publishes across the network.

Red Hat Automation Services Catalog API
Red Hat Ansible Automation Platform Access Policies API
Red Hat Ansible Automation Platform Acs: File API
Red Hat Ansible Automation Platform Activation Instances API
Red Hat Ansible Automation Platform Activations API
Red Hat Ansible Automation Platform Activity Stream API
Red Hat Ansible Automation Platform Ad Hoc Command Events API
Red Hat Ansible Automation Platform Ad Hoc Commands API
Red Hat Ansible Automation Platform AI API
Red Hat Ansible Automation Platform Analytics API
Red Hat Ansible Automation Platform Ansible: Collections API
Red Hat Ansible Automation Platform Api: API
Where this information came from

This is an independent, third-party profile of Red Hat Ansible Automation Platform Inventory Sources API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.