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 Credential Input Sources API

The credential_input_sources API from Red Hat Ansible Automation Platform — 4 operation(s) for credential_input_sources.

Red Hat Ansible Automation Platform Credential Input 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.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 11 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, /api/eda/v1.

11 operations 4 paths 10 schemas 2 DELETE4 GET2 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://controller-host/api/v2/
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Red Hat Ansible Automation Platform Credential Input Sources API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-DAB-JW-TOKEN (EDAJWTAuthentication). An API key is passed in the cookie as sessionid (cookieAuth).

Paths & Operations 11

Across 4 paths, the API surfaces 11 operations — 2 DELETE, 4 GET, 2 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

credential_input_sources 11
GET
/api/v2/credential_input_sources/
Credential input sources list
credential_input_sources_list 7 params → 200
POST
/api/v2/credential_input_sources/
Credential input sources create
credential_input_sources_create body → 201
GET
/api/v2/credential_input_sources/{id}/
Credential input sources retrieve
credential_input_sources_retrieve 1 param → 200
PUT
/api/v2/credential_input_sources/{id}/
Credential input sources update
credential_input_sources_update 1 param body → 200
PATCH
/api/v2/credential_input_sources/{id}/
Credential input sources partial update
credential_input_sources_partial_update 1 param body → 200
DELETE
/api/v2/credential_input_sources/{id}/
Credential input sources destroy
credential_input_sources_destroy 1 param → 204
GET
/credential-input-sources/
Credential input sources list
getCredentialInputSources 4 params → 200
POST
/credential-input-sources/
Credential input sources create
postCredentialInputSources body → 201
GET
/credential-input-sources/{id}/
Credential input sources retrieve
getCredentialInputSourcesById 2 params → 200
PATCH
/credential-input-sources/{id}/
Credential input sources partial update
patchCredentialInputSourcesById 1 param body → 200
DELETE
/credential-input-sources/{id}/
Credential input sources destroy
deleteCredentialInputSourcesById 1 param → 204

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are CredentialInputSource (12 properties), CredentialInputSource_2 (12 properties), CredentialInputSourceCreate (6 properties), PatchedCredentialInputSourceUpdate (6 properties). Each schema is shown below with its type and property counts.

CredentialInputSource
object
12 properties 3 required
CredentialInputSourceRequest
object
5 properties 3 required
PaginatedCredentialInputSourceList
object
4 properties 2 required
PatchedCredentialInputSourceRequest
object
5 properties
PatchedCredentialInputSourceUpdate
object
Serializer used during update of the instance.
6 properties
EdaCredentialReference
object
4 properties 4 required
OrganizationRef
object
3 properties 2 required
PaginatedCredentialInputSourceList_2
object
6 properties
CredentialInputSourceCreate
object
Serializer used during the Create process of the instance.
6 properties 5 required
CredentialInputSource_2
object
Serializer used during a GET.
12 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

red-hat-ansible-automation-platform-credential-input-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 Credential Input 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.