Append a user message to an existing session and resume the agent. The session must be in a terminal state (idle, completed, or failed); sending to a session that is processing or queued returns 409 interaction_not_in_terminal_state.
api.gumloop.com only serves the non-streaming response above. To stream agent output as it’s produced, send the same request body (with stream: true) to the streaming host instead:
POST https://ws.gumloop.com/api/v1/sessions/{session_id}/messages
The response is text/event-stream (Server-Sent Events). With the Python SDK, client.sessions.stream_message(session_id, input="...") routes to ws.gumloop.com automatically and yields parsed StreamEvent objects.
If you send stream: true to api.gumloop.com by mistake, the response is a 400 whose body contains the correct streaming host so you can retry against it.
Documentation Index
Fetch the complete documentation index at: https://docs.gumloop.com/llms.txt
Use this file to discover all available pages before exploring further.
ID of the session to continue.
The next user message. Required. Also accepted as message for backwards compatibility.
"Now write a follow-up email."
Must be false (or omitted) when calling api.gumloop.com. Set to true only when calling ws.gumloop.com (see the streaming section above).