curl --request POST \
--url https://runchat.com/api/v1/job/{runchat_job_id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data @- <<EOF
{
"message": "Summarize today's incoming support tickets and post the digest to #support."
}
EOF{
"metadata": "<string>",
"messages": [
{}
],
"job_id": "<string>",
"runchat_id": "<string>",
"status": "success",
"error": "<string>"
}{
"error": "<string>"
}{
"error": "<string>"
}{
"error": "<string>"
}{
"error": "<string>"
}Endpoints
Trigger Agent Job with Message
Trigger an agent job and append a user message to the saved chat template before running the agent loop. Use this to wire webhooks into scheduled agents.
POST
/
job
/
{runchat_job_id}
curl --request POST \
--url https://runchat.com/api/v1/job/{runchat_job_id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data @- <<EOF
{
"message": "Summarize today's incoming support tickets and post the digest to #support."
}
EOF{
"metadata": "<string>",
"messages": [
{}
],
"job_id": "<string>",
"runchat_id": "<string>",
"status": "success",
"error": "<string>"
}{
"error": "<string>"
}{
"error": "<string>"
}{
"error": "<string>"
}{
"error": "<string>"
}Authorizations
Path Parameters
Body
application/json
Optional payload for triggering an agent job. If message is set it is appended as a user message after the saved chat template. If message is absent, the entire body is JSON-stringified and appended as the user message.
Response
Successful agent execution.
Response shape for agent-backed job runs.