Netcracker Balancing Rules Administration V3 API is one of 47 APIs that Netcracker publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Balancing Rules Administration V3. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.
This API exposes
9 operations
across 5 paths,
and defines 8 schemas.
It is described by OpenAPI 3.2.0, at version 6.13.2.
Requests are made against the base URL https://{apihub}.qubership.org.
9 operations5 paths8 schemas2 DELETE2 GET1 POST4 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.2.0
API Version
6.13.2
Base URL
https://{apihub}.qubership.org
Authentication
HTTP Bearer
Resource Areas
1
Authentication & Security 1
Netcracker Balancing Rules Administration V3 API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (SecurityScheme).
SecurityScheme — Authentication
Paths & Operations 9
Across 5 paths, the API surfaces 9 operations — 2 DELETE, 2 GET, 1 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.
Balancing Rules Administration V3 9
Allows to configure a logic of balancing logical databases over physical.
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are OnMicroserviceRuleRequest (3 properties), PermanentPerNamespaceRuleDTO (3 properties), RuleRegistrationRequest (3 properties), DebugRulesRequest (2 properties). Each schema is shown below with its type and property counts.
DebugRulesRequest
object
Debug rules request allows to validate a list of rules against a list of microservices to check what database is going to be assigned to each microservice
2 properties2 required
PermanentPerNamespaceRuleDTO
object
Rule allows to define in which physical database new logical databases should be created
3 properties3 required
OnMicroserviceRuleRequest
object
Rule registration request allows to add a new rule for the specific type of logical databases, which would be applied in specific order.
3 properties2 required
PermanentPerNamespaceRuleDeleteDTO
object
2 properties1 required
RuleOnMicroservice
object
Rule allows to define physical database for new logical databases on microservice
1 property1 required
RuleRegistrationRequest
object
Rule registration request allows to add a new rule for the specific type of logical databases, which would be applied in specific order.
3 properties1 required
RuleType
string
Rule type specified what configuration applies to which logic. - perNamespace rule would just use specified physical database for any new logical database in n…
RuleBody
object
Rule allows to define physical database for new logical databases
2 properties2 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
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.
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 Netcracker Balancing Rules Administration V3 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.
