Skip to content
remotehangar
RU Discuss a pilot
Menu

RemoteHangar API

Your interface. Shared assistants. One API.

Connect an internal portal, help desk or company product to a prepared RemoteHangar workspace. Users stay in your interface; the assistant works with configured sources and tools.

Explore your use case Example task
  1. Your interface
  2. Application backend
  3. RemoteHangar API
  4. Sources and tools

Keep the RemoteHangar token on your application backend. Never expose it in the user’s browser.

A foundation for assistants in your products

Continuing conversations

Associate a session with your external_chat_id and send follow-up messages to the same conversation.

Streamed answers and events

Receive text, tool activity and completion through SSE. Show execution progress in your own interface.

Prepared agents

Select a configured agent and MCP connections instead of rebuilding their setup in each application.

Execution control

Interrupt requests, close sessions and handle limits and failures through the API contract.

API / HTTP + SSE

From a portal conversation to an assistant session

Request structures from the existing API. Agent and connection identifiers come from your own installation.

01 / Open a session

POST /v1/sessions
Authorization: Bearer YOUR_REMOTEHANGAR_TOKEN
Content-Type: application/json

{
  "external_chat_id": "portal:project-42:conversation-7",
  "agent_id": "project-advisor"
}

02 / Send a question and read SSE

POST /v1/sessions/SESSION_KEY/prompts
Authorization: Bearer YOUR_REMOTEHANGAR_TOKEN
Content-Type: application/json
Accept: text/event-stream

{
  "prompt": "Which tasks are blocking the project launch? Cite your sources."
}

Store the session_key returned in the response and use it for follow-up messages. Creating again with the same external_chat_id returns the associated session.

Stream events

  • message_delta — answer fragment
  • tool_use / tool_result — tool activity
  • done — completion
  • error — failure

A contract your team can build on

The complete OpenAPI schema and interactive documentation are available in your installation when the API is enabled. Available methods and models depend on its configuration.

GET/v1/agents
Available agents
GET/v1/mcp-servers
Available MCP connections
POST/v1/sessions
Create or retrieve a session by external_chat_id
POST/v1/sessions/:key/prompts
Send a message and stream the result
POST/v1/sessions/:key/interrupt
Request an execution interrupt
DELETE/v1/sessions/:key
Close a session

One integration with clear boundaries

A RemoteHangar token authorizes your application. It is not a pay-as-you-go model-provider key: execution uses accounts connected in RemoteHangar and their available plans.

  • Separate RemoteHangar tokens with permitted API operations.

  • Source access through the assistant’s configured tools.

  • Limits and errors handled by your application.

  • Requests and necessary context sent to your chosen model provider.

Embed an assistant in one real process

Choose the interface, questions, sources and permitted actions. The pilot validates the user journey against agreed outcome criteria.

Discuss a pilot

We agree on timing, pricing and scope before the pilot starts.