Send a message

A conversation is a session: create it once, then send follow-up turns. Both verbs schedule work and return immediately — output arrives on the SSE journal tail, not in the response.

Create a session — POST /sessions

curl -X POST https://api.sectr.dev/sessions \
  -H "Authorization: Bearer $SECTR_INVOCATION_KEY" \
  -H "Content-Type: application/json" \
  -d '{"app": "support-agent", "route": "/chat", "input": {"message": "Where is order 123?"}}'

201 with the session id:

{ "session_id": "0198c7a2-…" }

• app — the app slug (as sectr deploy created it) or its id;
• route — which agent route handles the conversation (e.g. /chat; the app’s routes are in GET /apps/{id});
• input — opaque JSON, yours to define; it is journaled verbatim and arrives in the agent as ctx.input. The dashboard sends {"message": "…"} — any shape works if your agent reads it.

Creating the session starts executing your agent immediately.

Follow-up turns — POST /sessions/{id}/input

curl -X POST https://api.sectr.dev/sessions/$SESSION_ID/input \
  -H "Authorization: Bearer $SECTR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"input": {"message": "and a refund please"}}'

202 — the turn is scheduled. 409 means the session isn’t accepting input right now: mid-turn (the previous turn’s lease is live), awaiting an approval decision (decide it first — a new message would strand the unanswered tool call), or ended. A 409 after an errored turn is deliberately impossible: sending a fresh message is the recovery path.