Skip to main content
GET
CLI
A thread is the whole conversation with one contact: email, WhatsApp, SMS and Telegram together, the same threads your team sees in the inbox. See Inbox for the concepts.

Use Cases

  • Find who needs a person: needsAttention=true lists the threads where the AI handed over or is paused while the contact waits
  • Build your own inbox view: the same filters and tab counters as the app
  • Look up a contact’s thread: search matches the contact’s name, email or phone
To search what was written in the messages, use Search Threads.

Permissions

The API key needs the Inbox permission (Developer › API keys). Every call is scoped to the key’s workspace. assigned=me means the user who created the key; counters.mine is there when the key belongs to a user.
  • Get Thread: read the messages of a thread
  • MCP: agents connected to Minimo’s MCP server use minimo_inbox_list-threads, which returns the same objects (Inbox for your AI agent)

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

status
enum<string>
default:open

Default open.

Available options:
open,
closed,
snoozed,
all
channel
enum<string>

Only threads on this channel.

Available options:
whatsapp,
email,
sms,
telegram
unread
boolean

true = only threads with unread messages.

needsAttention
boolean

true = a person must answer: the AI handed over, or it is paused while the contact waits.

assigned
enum<string>
default:any

me = the user who created the key.

Available options:
any,
me,
unassigned

Contact's name, email or phone. To search what was written, use Search Threads.

Maximum string length: 200
page
integer
default:1
Required range: x >= 1
pageSize
integer
default:20
Required range: 1 <= x <= 50

Response

Threads, pagination and tab counters

data
object