bot

Bot Ingest Route

Changed on

Channel-memory ingestion. Stores messages ONLY for channels connected to a workspace (same channel-scoping rule as /answer): an unconnected channel stores nothing and returns connected=false so the bot can stop sending for a while.

Also the reply-trigger signal: bot_thread=true means at least one ingested human message replies/threads onto a bot-authored message, so the bot process should follow up via /answer (whose own rate limit throttles replies).

post/api/v1/bot/ingest

Request

  • Base URL
    https://api.minro.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.minro.com/api/v1/bot/ingest
  • Auth
    none declared

Query parameters

providerstring required
platform_user_idstring required
channel_idstring required

Request body

Response

Successful Response

Changes

  • 299da1f7604aRevision changes
    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

  • 2eae594b5490Revision changes
    • info

      the response's property default value {"request_id":"","timestamp":"2026-09-16T23:27:36.856600"} was removed for the status

    • info

      the response's property default value 2026-09-16T23:27:36.856600 was removed for the status