ask-feather

Send Message

Enqueue a turn (Phase 3 split contract): run the same fast pre-flight gates as before, commit a durable queued turn row, drop a job on the ask_feather worker queue, and return {turn_id}. The client then opens a separate …/turns/{turn_id}/stream request to watch it. The web process holds no DB connection and does no AI work past this point.

post/v1/ask-feather/sessions/{session_id}/messages

Path parameters

session_idstring uuid required

Request body

contentstring required
workflowstring nullable

Response

Successful Response

turn_idstring uuid required
statusstring required

Changes

Changed in 1 of the 3 revisions of this API.111

  • 5a5597ebb2d6111See the full diff
    • removed the success response with the status 200

      response-success-status-removed

    • the content request property's maxLength was set to 20000

      request-property-max-length-set

    • added the success response with the status 202

      response-success-status-added

    This revision also has 40 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog