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

DDL and MCP contract APIs.

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

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

This API exposes 10 operations across 10 paths, and defines 16 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.

10 operations 10 paths 16 schemas 10 GET

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, HTTP Basic, API Key, API Key
License
Resource Areas
1

Authentication & Security 6

Netcracker Contracts 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). It accepts HTTP basic authentication (BasicAuth). 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). 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.
  • BasicAuth — Login/password authentication.
  • 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

Paths & Operations 10

Across 10 paths, the API surfaces 10 operations — 10 GET. Each is listed below with its method, path, parameters, and response codes.

Contracts 10

DDL and MCP contract APIs.

GET
/api/v1/packages/{packageId}/versions/{version}/ddl/entities
Get DDL entities
getPackageVersionDdlEntities 5 params → 200301400401404500
GET
/api/v1/packages/{packageId}/versions/{version}/ddl/entities/{ddlEntityId}
Get DDL entity details
getPackageVersionDdlEntity 3 params → 200301401404500
GET
/api/v1/packages/{packageId}/versions/{version}/ddl/entities/{ddlEntityId}/changes
Get DDL entity changes
getPackageVersionDdlEntityChanges 7 params → 200301401404500
GET
/api/v1/packages/{packageId}/versions/{version}/ddl/changes
Get list of changed DDL entities
getPackageVersionDdlChanges 9 params → 200301401404500
GET
/api/v1/packages/{packageId}/versions/{version}/ddl/entities/{ddlEntityId}/changes/summary
Single DDL entity changes summary
getPackageVersionDdlEntityChangesSummary 6 params → 200301401404500
GET
/api/v1/packages/{packageId}/versions/{version}/ddl/export/entities
Export DDL entities to xlsx file
getPackageVersionDdlEntitiesExport 4 params → 200301400401404500
GET
/api/v1/packages/{packageId}/versions/{version}/ddl/export/changes
Export DDL changes to xlsx file
getPackageVersionDdlChangesExport 7 params → 200301400401404500
GET
/api/v1/packages/{packageId}/versions/{version}/mcp/{entity}
Get MCP contract entities
getPackageVersionMcpEntities 7 params → 200301400401404500
GET
/api/v1/packages/{packageId}/versions/{version}/mcp/{entity}/{mcpEntityId}
Get MCP contract entity details
getPackageVersionMcpEntity 4 params → 200301401404500
GET
/api/v1/packages/{packageId}/versions/{version}/mcp/export/{entity}
Export MCP contract entities to xlsx file
getPackageVersionMcpEntitiesExport 5 params → 200301400401404500

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are PackageVersionRef (9 properties), ChangeSummary (6 properties), McpEntity (6 properties), ErrorResponse (5 properties). Each schema is shown below with its type and property counts.

VersionStatusEnum
string
Package version status
DdlEntityChange
object
One side (current or previous) of a DDL entity in a changelog change entry.
ChangeReplace
object
Data of single operation change when change action = replace
4 properties
DdlEntityView
object
DDL entity as returned by the version GET list/details endpoints.
McpEntityView
object
MCP discovery contract entity as returned by the version GET list/details endpoints: the shared McpEntity plus (for dashboards) the package reference.
PackagesMap
object
A map of referenced package versions to the package version objects. The key is packageId@version@revision — three @-separated segments (note: the version fiel…
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
SingleOperationChange
PackageVersionRef
object
Package version reference
9 properties 5 required
DdlEntity
object
Identified DDL entity — its stable id and descriptor (kind/name/schemaName/description). The core shared by the build result and the API; each context adds its…
5 properties 5 required
ChangeRename
object
Data of single operation change when change action = rename.
4 properties
ChangeSummary
object
Numbers of changes between the current and previous published version.
6 properties
ChangeAdd
object
Data of single operation change when change action = add
2 properties
ChangeSeverity
string
Severity of the particular change.
ChangeRemove
object
Data of single operation change when change action = remove.
2 properties
McpEntity
object
MCP discovery contract entity. Holds the fields common to the API response and the mcp.json build-result index; each context adds its own fields via allOf.
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

netcracker-contracts-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 Contracts 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.