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 Teams API

The teams API from Red Hat Ansible Automation Platform — 19 operation(s) for teams.

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

This API exposes 30 operations across 19 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

30 operations 19 paths 29 schemas 2 DELETE15 GET2 PATCH9 POST2 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, HTTP Basic, OAuth 2.0, API Key
Resource Areas
1

Authentication & Security 5

Red Hat Ansible Automation Platform Teams API declares 5 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). It accepts HTTP basic authentication (Basic_Authentication). It supports OAuth 2.0 (OAuth2_Authentication) using the authorizationCode and password flows, exposing 2 scopes. An API key is passed in the cookie as gateway_sessionid (SessionAuthentication).

Paths & Operations 30

Across 19 paths, the API surfaces 30 operations — 2 DELETE, 15 GET, 2 PATCH, 9 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Teams 30
GET
/api/v2/teams/
Teams list
teams_list 7 params → 200
POST
/api/v2/teams/
Teams create
teams_create body → 201
GET
/api/v2/teams/{id}/
Teams retrieve
teams_retrieve 1 param → 200
PUT
/api/v2/teams/{id}/
Teams update
teams_update 1 param body → 200
PATCH
/api/v2/teams/{id}/
Teams partial update
teams_partial_update 1 param body → 200
DELETE
/api/v2/teams/{id}/
Teams destroy
teams_destroy 1 param → 204
GET
/api/v2/teams/{id}/access_list/
Teams access list list
teams_access_list_list 8 params → 200
GET
/api/v2/teams/{id}/activity_stream/
Teams activity stream list
teams_activity_stream_list 8 params → 200
GET
/api/v2/teams/{id}/credentials/
Teams credentials list
teams_credentials_list 8 params → 200
POST
/api/v2/teams/{id}/credentials/
Teams credentials create
teams_credentials_create 1 param body → 201
GET
/api/v2/teams/{id}/object_roles/
Teams object roles list
teams_object_roles_list 8 params → 200
GET
/api/v2/teams/{id}/projects/
Teams projects list
teams_projects_list 8 params → 200
GET
/api/v2/teams/{id}/roles/
Teams roles list
teams_roles_list 8 params → 200
POST
/api/v2/teams/{id}/roles/
Teams roles create
teams_roles_create 1 param → 201
GET
/api/v2/teams/{id}/users/
Teams users list
teams_users_list 8 params → 200
POST
/api/v2/teams/{id}/users/
Teams users create
teams_users_create 1 param body → 201
GET
/teams/
Teams list
getTeams 6 params → 200
GET
/teams/{id}/
Teams retrieve
getTeamsById 1 param → 200
GET
/api/gateway/v1/teams/
Teams list
getApiGatewayV1Teams 30 params → 200
POST
/api/gateway/v1/teams/
Teams create
postApiGatewayV1Teams body → 201
GET
/api/gateway/v1/teams/{id}/
Teams retrieve
getApiGatewayV1TeamsById 1 param → 200
PUT
/api/gateway/v1/teams/{id}/
Teams update
putApiGatewayV1TeamsById 1 param body → 200
PATCH
/api/gateway/v1/teams/{id}/
Teams partial update
patchApiGatewayV1TeamsById 1 param body → 200
DELETE
/api/gateway/v1/teams/{id}/
Teams destroy
deleteApiGatewayV1TeamsById 1 param → 204
GET
/api/gateway/v1/teams/{id}/admins/deprecated
Teams admins list
teams_admins_list 51 params → 200
POST
/api/gateway/v1/teams/{id}/admins/associate/deprecated
Teams admins associate create
teams_admins_associate_create 1 param body → 200
POST
/api/gateway/v1/teams/{id}/admins/disassociate/deprecated
Teams admins disassociate create
teams_admins_disassociate_create 1 param body → 200
GET
/api/gateway/v1/teams/{id}/users/deprecated
Teams users list
getApiGatewayV1TeamsByIdUsers 51 params → 200
POST
/api/gateway/v1/teams/{id}/users/associate/deprecated
Teams users associate create
teams_users_associate_create 1 param body → 200
POST
/api/gateway/v1/teams/{id}/users/disassociate/deprecated
Teams users disassociate create
teams_users_disassociate_create 1 param body → 200

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are Project (33 properties), User_2 (21 properties), ResourceAccessListElement (15 properties), User (15 properties). Each schema is shown below with its type and property counts.

RoleSerializerWithParentAccess
object
7 properties
PaginatedUserList
object
4 properties 2 required
ActivityStream
object
13 properties 3 required
Role
object
7 properties
PaginatedProjectList
object
4 properties 2 required
TeamCredentialSerializerCreate
object
15 properties 2 required
Project
object
33 properties 1 required
PatchedTeamRequest
object
3 properties
PaginatedTeamCredentialSerializerCreateList
object
4 properties 2 required
User
object
15 properties 1 required
TeamCredentialSerializerCreateRequest
object
5 properties 2 required
UserRequest
object
7 properties 1 required
PaginatedActivityStreamList
object
4 properties 2 required
ResourceAccessListElement
object
15 properties 1 required
PaginatedTeamList
object
4 properties 2 required
PaginatedRoleList
object
4 properties 2 required
PaginatedRoleSerializerWithParentAccessList
object
4 properties 2 required
TeamRequest
object
3 properties 2 required
Team
object
10 properties 2 required
PaginatedResourceAccessListElementList
object
4 properties 2 required
Team_2
object
9 properties 8 required
PaginatedTeamList_2
object
6 properties
OrganizationRef
object
3 properties 2 required
TeamDetail
object
9 properties 8 required
UserDisassociate
object
Serializer used for removing objects that are currently associated via a many-to-many relationship
1 property 1 required
UserAssociate
object
Serializer used for adding objects to a many-to-many relationship
1 property 1 required
Team_3
object
Class to be used by apps to check permissions to related objects This is a core part of integrating permission checks with REST APIs. Full enablement of checks…
11 properties 2 required
User_2
object
Disallows editing of system user and enforces superuser requirement.
21 properties 1 required
PatchedTeam
object
Class to be used by apps to check permissions to related objects This is a core part of integrating permission checks with REST APIs. Full enablement of checks…
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

red-hat-ansible-automation-platform-teams-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 Teams 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.