Send a message to a run
Changed onSends a person's message to an agent-mode run. To a run that is running or paused, the run's model reads it before its next step, as a turn from the person running the task, and the run's stream carries it as a user_message event, its body the message, once the run's phone has it. A message never resumes a paused run: answer the pause with :resume. A run holds at most 20 unread messages, and the edge refuses one past that, or one that arrives as the run finishes, which may then never be read or shown. To a run that ended (completed, failed or cancelled) while it still holds its phone (keep_alive_expires_at is in the future), the message starts the run's next turn on the same phone, and the run goes back to queued. Returns the run as it is. A code run, a queued or scheduled run, a run whose hold has ended, or a run whose phone cannot take messages yet is 409; an empty message, or one over 64 KiB, is 400.
Request
- Base URL/api/v1 (relative, and the document was published on a file host, not at the API’s origin)
- AuthAPI key in header X-Axilio-Api-Key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
The run's id.
Request body
Example request
{
"$schema": "/api/v1/AgentRunSendMessageRequest.json"
}Response
Accepted
Example response
{
"$schema": "/api/v1/RunResponse.json"
}Changes
- info
endpoint added
- info