list_tickets / get_ticket. To be told when a ticket changes in FlowIQ, register a ticket webhook.
Request
POST to the same address works too.
{ticket} is the ticket’s id, or its number as your team sees it, for example FLW-261122-001 (any case). If FlowIQ opened a case in your system for the ticket, the number is the externalCaseNumber it sent you.
Use an organisation API key with write permission (Settings, API Keys) as a Bearer token. The key decides which account you change; a ticket on another account answers 404.
Send at least one of
status, note or assigned_to.
What FlowIQ does
- Status: the ticket moves and the change is recorded in its status history (
by: "api"). Resolving stampsresolved_at; moving a resolved ticket back toopenorin_progresscounts as a reopen. - Notes:
noteandassigned_toare written into the ticket’s Notes, one line per call, for example[2026-11-22 19:45, API] Assigned to Sam Smith. That is what the team sees on the ticket in FlowIQ. - The AI: if the account switches the AI back on when a ticket is resolved, resolving through this endpoint does the same.
- Nothing is sent to the customer.
- The change fires the usual ticket webhooks (
ticket.updated,ticket.status_changed,ticket.resolved, …).
"updated": false.
Response
ticket is the full ticket, the same object get_ticket returns (shortened above).
Errors
Every answer carries
X-Request-Id; quote it to support.

