Evaluate canonical state and push eligible human-attention nudges to the workspace's active Telegram destination. This endpoint is the EXPLICIT trigger; in addition, a server-side scheduler runs the same evaluation every hour and delivers only to channels whose own local hour is inside their configured window, and its deliveries carry trigger 'scheduled' and count against the same daily cap as explicit pushes. Sources are the canonical temporal states needs_decision, overdue (needs_feedback) and needs_timing, in the same order /state next_priorities uses. Paced per channel (max_nudges_per_hour default 1, max_nudges_per_day default 6, both owner-configurable) across explicit and scheduled deliveries, and deduped by state fingerprint: an unchanged ask is never re-sent. Anything that does not fit the pace is QUEUED, never dropped — see attention_queue in GET /state and the digest.

post/workspace/channels/telegram/push

Request

  • Base URL: https://forbiz.io/api/public/agent
  • URL: https://forbiz.io/api/public/agent/workspace/channels/telegram/push
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Recommended on every mutating request. A replay with the same key is NOT applied twice: the server answers { ok, idempotent_replay: true, first_seen_at, status } describing the first attempt.

Request body

limitinteger

Response

Push result

okboolean
channel_idstring
sentobject[]
skipped_duplicatesinteger
failedinteger
eligibleinteger
daily_cap_remaininginteger

Changes

No recorded changes to this operation across all 1 revision of this API.