Netcracker AI Chat API
APIs for AI chat assistant.Each user has their own chat list; chats are persisted on the server with a configurable TTL and pinning support.Conversations support streaming responses (SSE) and automatic context compaction (old messages are re-packed into a summary when the conversation approaches the model's context window, so that older facts are preserved instead of being silently dropped by the LLM).
Netcracker AI Chat API is one of 40 APIs that Netcracker publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include AI Chat. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.
This API exposes 8 operations across 4 paths, and defines 17 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 6
Netcracker AI Chat 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 8
Across 4 paths, the API surfaces 8 operations — 1 DELETE, 3 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.
APIs for AI chat assistant. Each user has their own chat list; chats are persisted on the server with a configurable TTL and pinning support. Conversations support streaming respo…
Schemas 17
The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are AiChatMessage (6 properties), AiChat (6 properties), AiChatStreamToolCompletedEvent (5 properties), ErrorResponse (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Netcracker 12
Other APIs Netcracker publishes across the network.
This is an independent, third-party profile of Netcracker AI Chat 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.