Skip to content

channels.post

Say something to an agent, a channel or Decibyl.

Reference

POST/api/v1/timeline/message

Auth
API key in X-API-Key
Content
application/json
Returns
200 · PostMessageResponse

Say something in a channel, and hand it to whichever bots it addressed. The message is recorded as an ``agent_event`` rather than in a table of its own. That is not thrift: a channel is a thread of what happened there, and a person asking for something is one of the things that happened. Keeping messages beside outcomes, failures and deliverables means the timeline reads as a conversation instead of two logs interleaved by a screen -- and every reader already has tenancy, the visibility gate and the cursor. The reply is enqueued rather than awaited. A bot's turn is an LLM call and a person who has just pressed enter should see their own message immediately; a request that blocks until a bot has thought is a request that times out on the one occasion the model is slow.

Arguments

ArgumentInTypeRequiredDescription
folder_idbodyintegeroptional
workflow_idbodyintegeroptional
assistantbodybooleandefault false
textbodystringdefault ""
attachmentsbodyAttachment[]optional
presetbodystringoptional
thread_idbodystringoptional
helperbodystringoptional

Example request

curl -X POST "https://api.decibyl.ai/api/v1/timeline/message" \
  -H "X-API-Key: dcb_your_key" \
  -H "Content-Type: application/json" \
  -d '{"folder_id":1,"workflow_id":1,"assistant":false,"text":"","attachments":[{"document_uuid":"string","filename":"string","size_bytes":0}],"preset":"string","thread_id":"string","helper":"string"}'

Response

{
  "asked": [
    1
  ],
  "unknown": [
    "string"
  ],
  "ambiguous": [
    "string"
  ]
}

Errors

StatusWhen
404Not found
422Validation Error