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

Netcracker Roles API

APIs for role management.

Netcracker Roles API is one of 40 APIs that Netcracker publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Roles. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 14 operations across 9 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2026.1.

Requests are made against a single base URL, https://{apihub}.qubership.org.

14 operations 9 paths 9 schemas 3 DELETE5 GET2 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026.1
Base URL
https://{apihub}.qubership.org
Authentication
HTTP Bearer, API Key, API Key, API Key, API Key, HTTP Basic
License
Resource Areas
1

Authentication & Security 6

Netcracker Roles API declares 6 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). An API key is passed in the cookie as apihub-access-token (CookieAuth). An API key is passed in the header as api-key (api-key). An API key is passed in the header as X-Personal-Access-Token (PersonalAccessToken). An API key is passed in the cookie as apihub-refresh-token (RefreshTokenAuth). It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token authentication (JWT). Default security scheme for API usage. Provide Authorization: Bearer .
  • CookieAuth — Authentication via the apihub-access-token cookie.
  • api-key — API key authentication. Send the key in the api-key header.
  • PersonalAccessToken — Personal access token authentication. Send the token in the X-Personal-Access-Token header; use for user-issued/script access.
  • RefreshTokenAuth — Authentication via refresh token cookie
  • BasicAuth — Login/password authentication.

Paths & Operations 14

Across 9 paths, the API surfaces 14 operations — 3 DELETE, 5 GET, 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Roles 14

APIs for role management.

POST
/api/v2/roles
Create a new role
postRoles body → 201400401403500
GET
/api/v2/roles
Get list of existing roles
getRoles → 200401403500
PATCH
/api/v2/roles/{roleId}
Update role
patchRolesId 1 param body → 204400401403404500
DELETE
/api/v2/roles/{roleId}
Delete role
deleteRolesId 1 param → 204401403404500
POST
/api/v2/roles/changeOrder
Update the roles order
postRolesChangeOrder body → 204400401403500
GET
/api/v2/admins
Get list of system administrators
getAdmins → 200401403500
POST
/api/v2/admins
Add a system administrator
postAdmins body → 201400401500
DELETE
/api/v2/admins/{userId}
Delete system administrator
deleteAdminsId 1 param → 204401404403500
GET
/api/v2/permissions
Get list of permissions
getPermissions → 200401403500
GET
/api/v2/packages/{packageId}/availableRoles
Get list of available roles for package
getPackagesIdAvailableRoles 2 params → 200301401404500
POST
/api/v2/packages/{packageId}/members
Add members to the package
postPackagesIdMembers 1 param body → 201301400401403404500
GET
/api/v2/packages/{packageId}/members
Get the package's members list
getPackagesIdMembers 1 param → 200301401403404500
PATCH
/api/v2/packages/{packageId}/members/{userId}
Package member update
patchPackagesIdMembersId 2 params body → 204301400401403404500
DELETE
/api/v2/packages/{packageId}/members/{userId}
Package member delete
deletePackagesIdMembersId 2 params → 200204301401403404500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (5 properties), User_2 (4 properties), User (4 properties), Member (2 properties). Each schema is shown below with its type and property counts.

User
object
Represents an APIHUB user returned by administration endpoints.
4 properties 1 required
RoleCreate
object
Payload for creating a role, including the role name and the permissions to assign.
2 properties 2 required
ErrorResponse
object
Standard error response returned for failed requests. Includes HTTP status, internal error code, human-readable message, optional message parameters, and optio…
5 properties 3 required
Permission
string
Permission identifier that grants a specific capability when assigned to a role.
Role
object
Represents a role with its identifier, display name, and assigned permissions.
2 properties 3 required
MemberCreate
object
Assign users and role to the package
2 properties 2 required
Member
object
User and assigned role
2 properties 2 required
User_2
object
Represents an APIHUB user with identity and profile information returned by API endpoints.
4 properties 1 required
Permission_2
string
Permission

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

netcracker-roles-api-openapi.yml Raw ↑

Other APIs Netcracker publishes across the network.

Netcracker Admin API
Netcracker Aggregated Database Administration No Namespace Controller V 3 API
Netcracker AI Chat API
Netcracker API version controller API
Netcracker Auth API
Netcracker Backup & Restore API
Netcracker Backups administration API
Netcracker Balancing Rules Administration V3 API
Netcracker Blue Green Controller V 1 API
Netcracker Changes API
Netcracker Composite Controller API
Netcracker Config Controller V 1 API
Where this information came from

This is an independent, third-party profile of Netcracker Roles 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.