Send Message (Non Streaming)

Send Message (Non Streaming) allows a client application to send a user message to an AI agent and receive a complete AI-generated response in a single request.

This endpoint is designed for chat interfaces, web chat widgets, support bots, messaging integrations, customer support automation, lead qualification bots, and internal knowledge assistants.

The client sends the user query along with the project ID, chatbot ID, and user-specific context. The AI agent processes the request and returns a response based on the chatbot configuration, knowledge base, conversation context, and available tools.

Endpoint

Request Body

{
  "query": "Hello",
  "pid": "3..",
  "chatbot_id": "DKDvwn...",
  "user_context": {
    "session_id": "6ff922ed-9884-4430-83c9-7ac83a7b0574",
    "platform": "web"
  }
}

Request Parameters

Field	Type	Required	Description
`query`	string	Yes	User message or question sent to the chatbot.
`pid`	string	Yes	Project ID associated with the chatbot.
`chatbot_id`	string	Yes	Unique chatbot identifier that should process the message.
`user_context`	object	Yes	Additional context about the user, session, channel, or client application.
`user_context.session_id`	string	No	Unique session identifier used to continue or group messages in the same conversation.
`user_context.platform`	string	Yes	Platform or channel where the message originated. Example: `web`.

Success Response

{
  "message": "Success",
  "data": {
    "answer": "Hello! How can I help you with your setup today?",
    "session_id": "6ff922ed-9884-4430-83c9-7ac83a7b0574"
  }
}

Response Fields

Root

Field	Type	Description
`message`	string	Status message for the chat request.
`data`	object	Contains the AI-generated response and conversation session details.

`data`

Field	Type	Description
`answer`	string	AI-generated response returned by the chatbot.
`session_id`	string	Conversation session identifier associated with the response.

Error Responses

400 Bad Request

Returned when the request body is invalid or required fields are missing.

{
  "message": "Bad Request",
  "error": {
    "code": "BAD_REQUEST",
    "detail": "Invalid request body or missing required fields."
  }
}

401 Unauthorized

Returned when the request does not include a valid bearer token.

{
  "message": "Unauthorized",
  "error": {
    "code": "UNAUTHORIZED",
    "detail": "Authentication token is missing or invalid."
  }
}

Notes

Use this endpoint when you want the full response returned at once.

For real-time typing effects or token-by-token responses, use the streaming message API instead.

Pass the same session_id in user_context to continue an existing conversation.

If session_id is not provided, your backend may generate or assign a new session depending on implementation.

The chatbot_id must belong to the specified project ID.

The response may depend on the chatbot’s knowledge base, linked assets, configured prompts, tools, and conversation history.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location 'https://agents.robofy.ai/v1/ai-agent/chat' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "query": "Hello", "pid": "3..", "chatbot_id": "DKDvwn...", "user_context": { "session_id": "6ff922ed-9884-4430-83c9-7ac83a7b0574", "platfrom": "web" } }'

Send Message (Non Streaming)

Endpoint#

Request Body#

Request Parameters#

Success Response#

Response Fields#

Root#

data#

Error Responses#

400 Bad Request#

401 Unauthorized#

Notes#

Request

Responses