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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Red Hat Ansible Automation Platform

Red Hat Ansible Automation Platform Repositories: Container-Push API

The Repositories: Container-Push API from Red Hat Ansible Automation Platform — 11 operation(s) for repositories: container-push.

Documentation Provider Profile APIs.io OpenAPI GitHub

Red Hat Ansible Automation Platform Repositories: Container-Push 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 Repositories: Container-Push. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 13 operations across 11 paths, and defines 15 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/.

13 operations 11 paths 15 schemas 4 GET1 PATCH7 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/
Contact
Automation Hub Team
License
GPLv2+
Resource Areas
1

Paths & Operations 13

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

Repositories: Container-Push 13
GET
/api/automation-hub/pulp/api/v3/repositories/container/container-push/
List container push repositorys
repositories_container_container_push_list 29 params → 200
GET
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/
Inspect a container push repository
repositories_container_container_push_read 3 params → 200
PUT
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/
Update a container push repository
repositories_container_container_push_update 1 param body → 202
PATCH
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/
Update a container push repository
repositories_container_container_push_partial_update 1 param body → 202
POST
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/add_role/
Add a role
repositories_container_container_push_add_role 1 param body → 201
GET
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/list_roles/
List roles
repositories_container_container_push_list_roles 3 params → 200
GET
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/my_permissions/
List user permissions
repositories_container_container_push_my_permissions 3 params → 200
POST
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/remove_image/
Delete an image from a repository
repositories_container_container_push_remove_image 1 param body → 202
POST
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/remove_role/
Remove a role
repositories_container_container_push_remove_role 1 param body → 201
POST
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/remove_signatures/
Repositories container container push remove signatures
repositories_container_container_push_remove_signatures 1 param body → 200
POST
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/sign/
Sign images in the repo
repositories_container_container_push_sign 1 param body → 202
POST
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/tag/
Create a Tag
repositories_container_container_push_tag 1 param body → 202
POST
/api/automation-hub/pulp/api/v3/repositories/container/container-push/{pulp_id}/untag/
Delete a tag
repositories_container_container_push_untag 1 param body → 202

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are container.ContainerPushRepositoryResponse (10 properties), container.ContainerPushRepository (5 properties), Patchedcontainer.ContainerPushRepository (5 properties), Paginatedcontainer.ContainerPushRepositoryResponseList (4 properties). Each schema is shown below with its type and property counts.

Patchedcontainer.ContainerPushRepository
object
Serializer for Container Push Repositories.
5 properties
TagImage
object
A serializer for parsing and validating data associated with a manifest tagging.
2 properties 2 required
RemoveSignatures
object
A serializer for parsing and validating data associated with the signatures removal.
1 property 1 required
RemoveImage
object
A serializer for parsing and validating data associated with the image removal.
1 property 1 required
MyPermissionsResponse
object
1 property 1 required
container.ContainerPushRepository
object
Serializer for Container Push Repositories.
5 properties 1 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
AsyncOperationResponse
object
Serializer for asynchronous operations.
1 property 1 required
RemoveSignaturesResponse
object
A serializer for parsing and validating data associated with the signatures removal.
1 property 1 required
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
RepositorySign
object
Serializer for container images signing.
3 properties
Paginatedcontainer.ContainerPushRepositoryResponseList
object
4 properties 2 required
ObjectRolesResponse
object
1 property 1 required
UnTagImage
object
A serializer for parsing and validating data associated with a manifest untagging.
1 property 1 required
container.ContainerPushRepositoryResponse
object
Serializer for Container Push Repositories.
10 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

red-hat-ansible-automation-platform-repositories-container-push-api-openapi.yml Raw ↑

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

Red Hat Automation Services Catalog API
AE Profile APIs.io
Red Hat Ansible Automation Platform Access Policies API
AE Profile APIs.io
Red Hat Ansible Automation Platform Acs: File API
AE Profile APIs.io
Red Hat Ansible Automation Platform Activation Instances API
AE Profile APIs.io
Red Hat Ansible Automation Platform Activations API
AE Profile APIs.io
Red Hat Ansible Automation Platform Activity Stream API
AE Profile APIs.io
Red Hat Ansible Automation Platform Ad Hoc Command Events API
AE Profile APIs.io
Red Hat Ansible Automation Platform Ad Hoc Commands API
AE Profile APIs.io
Red Hat Ansible Automation Platform AI API
AE Profile APIs.io
Red Hat Ansible Automation Platform Analytics API
AE Profile APIs.io
Red Hat Ansible Automation Platform Ansible: Collections API
AE Profile APIs.io
Red Hat Ansible Automation Platform Api: API
AE Profile APIs.io
#Repositories: Container-Push
← Back to R APIs
API Details
ID
red-hat-ansible-automation-platform:red-hat-ansible-automation-platform-repositories-container-push-api
Base URL
https://controller-host/api/v2/
Docs
https://access.redhat.com/documentation/en-us/red_hat_ansible_automation_platform/
Provider
Red Hat Ansible Automation Platform
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=red-hat-ansible-automation-platform-repositories-container-push-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/red-hat-ansible-automation-platform-repositories-container-push-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Red Hat Ansible Automation Platform Repositories: Container-Push 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.