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 Upstream Pulps API

The Upstream-Pulps API from Red Hat Ansible Automation Platform — 7 operation(s) for upstream-pulps.

Red Hat Ansible Automation Platform Upstream Pulps 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 Upstream-Pulps. 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 7 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version v3.

Requests are made against a single base URL, http://automation-hub-backend-cwa.automation-hub-prod.svc.cluster.local:8000/.

11 operations 7 paths 9 schemas 1 DELETE4 GET1 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 11

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

Upstream-Pulps 11
GET
/api/automation-hub/pulp/api/v3/upstream-pulps/
List upstream pulps
upstream_pulps_list 4 params → 200
POST
/api/automation-hub/pulp/api/v3/upstream-pulps/
Create an upstream pulp
upstream_pulps_create body → 201
GET
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/
Inspect an upstream pulp
upstream_pulps_read 3 params → 200
PUT
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/
Update an upstream pulp
upstream_pulps_update 1 param body → 200
PATCH
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/
Update an upstream pulp
upstream_pulps_partial_update 1 param body → 200
DELETE
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/
Delete an upstream pulp
upstream_pulps_delete 1 param → 204
POST
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/add_role/
Add a role
upstream_pulps_add_role 1 param body → 201
GET
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/list_roles/
List roles
upstream_pulps_list_roles 3 params → 200
GET
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/my_permissions/
List user permissions
upstream_pulps_my_permissions 3 params → 200
POST
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/remove_role/
Remove a role
upstream_pulps_remove_role 1 param body → 201
POST
/api/automation-hub/pulp/api/v3/upstream-pulps/{pulp_id}/replicate/
Replicate
upstream_pulps_replicate 1 param → 202

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are UpstreamPulpResponse (12 properties), UpstreamPulp (11 properties), PatchedUpstreamPulp (11 properties), PaginatedUpstreamPulpResponseList (4 properties). Each schema is shown below with its type and property counts.

MyPermissionsResponse
object
1 property 1 required
UpstreamPulp
object
Serializer for a Server.
11 properties 3 required
NestedRole
object
Serializer to add/remove object roles to/from users/groups. This is used in conjunction with pulpcore.app.viewsets.base.RolesMixin and requires the underlying…
3 properties 1 required
TaskGroupOperationResponse
object
Serializer for asynchronous operations that return a task group.
1 property 1 required
PaginatedUpstreamPulpResponseList
object
4 properties 2 required
UpstreamPulpResponse
object
Serializer for a Server.
12 properties 3 required
PatchedUpstreamPulp
object
Serializer for a Server.
11 properties
NestedRoleResponse
object
Serializer to add/remove object roles to/from users/groups. This is used in conjunction with pulpcore.app.viewsets.base.RolesMixin and requires the underlying…
3 properties 1 required
ObjectRolesResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

red-hat-ansible-automation-platform-upstream-pulps-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 Upstream Pulps 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.