Wabee Agent Core API
Wabee Agent Core API (v1)
Wabee Agent Core API enables developers to interact with an AI agent in a custom, secure and flexible manner through REST API calls.
One can build applications to interact with the agent API to complete a task using any of the Agents endpoints which allow for both text streaming and direct JSON response. The Memory endpoints are useful for managing the agent memory programatically. Moreover, the Metrics endpoints provide an interface for monitoring the underlying Agent in terms of latency, health, token consumption and much more.
Request
Retrieves the complete conversation history and metadata for a specific session.
The session data includes:
- All messages exchanged between user and AI
- Timestamps for each message
- Additional context like reasoning steps for AI responses
- Session metadata
Each message contains:
- role: Either 'human' or 'ai'
- content: The actual message text
- timestamp: When the message was sent
- additional_context: Extra information like reasoning steps (for AI messages)
- Mock serverhttps://api.docs.wabee.ai/_mock/openapi/core/v1/sessions/{session_id}
- Production serverhttps://<your_agent_uri>.wabee.ai/core/v1/sessions/{session_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.docs.wabee.ai/_mock/openapi/core/v1/sessions/{session_id}' \
-H 'x-wabee-access: YOUR_API_KEY_HERE'Successful Response
The messages exchanged during the session.
The role of the message sender. Can be either 'user' or 'assistant'.
The content of the message.
The content of the message.
The timestamp of the message in seconds since the Unix epoch.
{ "session_id": "VSkqDuv", "messages": [ { … }, { … } ] }
Request
Returns a paginated list of all available chat sessions.
The response includes:
- List of session summaries
- Pagination information
- Total count of returned sessions
Each session summary contains:
- session_id: Unique identifier for the session
- checkpoint_id: Internal reference ID
- short_name: Brief description based on first message
Use the query parameters to navigate through pages:
- before: Get sessions before this session ID
- limit: Number of sessions per page (1-50)
Sessions are ordered by most recent first. Empty sessions (no messages) are automatically filtered out.
- Mock serverhttps://api.docs.wabee.ai/_mock/openapi/core/v1/sessions
- Production serverhttps://<your_agent_uri>.wabee.ai/core/v1/sessions
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.docs.wabee.ai/_mock/openapi/core/v1/sessions?before=string&limit=45' \
-H 'x-wabee-access: YOUR_API_KEY_HERE'{ "sessions": [ { … } ], "offset": "1efb5872-be2a-653c-8003-f96d250d9bed", "count": 1 }