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 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.

8 operations 4 paths 17 schemas 1 DELETE3 GET1 PATCH3 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, HTTP Basic, API Key, API Key
License
Resource Areas
1

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.

AI Chat 8

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…

GET
/api/v1/ai-chat/chats
List chats of the current user.
listAiChats 3 params → 200401500
POST
/api/v1/ai-chat/chats
Create a new chat.
createAiChat body → 201400401500
GET
/api/v1/ai-chat/chats/{chatId}
Get chat metadata.
getAiChat 1 param → 200401404500
PATCH
/api/v1/ai-chat/chats/{chatId}
Update chat (rename / pin / unpin).
updateAiChat 1 param body → 200400401404500
DELETE
/api/v1/ai-chat/chats/{chatId}
Delete a chat.
deleteAiChat 1 param → 204401404500
GET
/api/v1/ai-chat/chats/{chatId}/messages
List chat messages.
listAiChatMessages 3 params → 200401404500
POST
/api/v1/ai-chat/chats/{chatId}/messages
Send a message (non-streaming).
sendAiChatMessage 1 param body → 200400401404500
POST
/api/v1/ai-chat/chats/{chatId}/messages/stream
Send a message with streaming response (SSE).
sendAiChatMessageStream 1 param body → 200400401404500

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.

AiChatCreateRequest
object
Optional payload for creating a new chat.
1 property
AiChatSendMessageResponse
object
Non-streaming response after a user message has been processed.
2 properties 2 required
AiChatStreamAssistantCompletedEvent
object
Terminal event for the assistant message. Carries the full final markdown (including any inline links to generated files).
2 properties 2 required
AiChatToolInvocation
object
Minimal, UI-facing descriptor of an MCP tool call that happened while producing an assistant message. The server intentionally does not expose tool arguments o…
3 properties 2 required
AiChatStreamToolStartedEvent
object
Emitted when the assistant decides to call an MCP tool. Multiple tool events may appear between message.assistant.start and message.assistant.completed.
3 properties 3 required
AiChatStreamDoneEvent
object
Terminal marker. Always the last event on a successful stream.
1 property 1 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
AiChatUpdateRequest
object
Partial update of a chat. Only fields present in the request are modified. At least one field must be supplied.
2 properties
AiChat
object
AI chat metadata (messages are not included).
6 properties 5 required
AiChatStreamErrorEvent
object
Emitted when the turn cannot be completed. After this event the server closes the stream without sending done.
3 properties 3 required
AiChatStreamAssistantStartEvent
object
Emitted once, right before the first message.assistant.delta event.
2 properties 2 required
AiChatMessage
object
A single chat message visible to the client. Assistant messages always carry markdown-formatted content; user messages carry raw text.
6 properties 4 required
AiChatStreamEvent
object
Documentation-only schema describing the shape of a single SSE event payload. The wire format is not JSON — each event is framed as: event: data: where the lin…
1 required
AiChatStreamAssistantDeltaEvent
object
Incremental markdown chunk for the assistant message. The client is expected to simply concatenate delta values in the order received.
2 properties 2 required
AiChatSendMessageRequest
object
Request body for sending a new user message. The body carries only the new message — never the full history.
2 properties 1 required
AiChatStreamToolCompletedEvent
object
Paired with the corresponding tool.started event.
5 properties 4 required
AiChatStreamContextCompactedEvent
object
Emitted at most once per turn, before the assistant starts streaming, if the server had to auto-compact earlier history. The client may use this signal to visu…
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

netcracker-ai-chat-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 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
Netcracker Contracts API
Where this information came from

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.