VEverdun
Conversations

List Conversations

Keyset page of the caller's threads, newest activity first.

status defaults to open and is an ADDITION to the brief's route list: without it an archived thread with no further inbound would be stranded out of reach.

order, parent_id, account_id, site_id and q are the inbox's sort / scope / search controls (owner ask 2026-09-22, "like the History tab"). All optional; omitted, the list is byte-identical to before.

get/conversations

Request

  • Base URL
    https://api.verdun.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.verdun.ai/conversations
  • Auth
    HTTP bearer

Query parameters

filterstring
statusstring
limitinteger
cursorstring nullable
order'desc' | 'asc'

Sort by last activity: desc newest first (the default), asc oldest first. Same vocabulary as GET /events/history. A cursor is only valid under the order it was minted with.

parent_idstring nullable

Only threads of this client. Out of scope matches nothing (never 403).

account_idstring nullable

Only threads whose SITE is under this account. A client-wide thread has no site and so never matches an account.

site_idstring nullable

Only threads on this site.

qstring nullable

Keyword search, History's rules: whitespace-split AND-ed terms, each matched case-insensitively against the contact name, client / account / site names, the customer's number (3+ digits) and every message body in the thread.

Response

Successful Response

next_cursorstring nullable

Keyset cursor for the next page. Keyset, not offset: inbound replies reorder this list continuously.

Example response

{
  "items": [
    {
      "verdun_number": "+18555550119",
      "customer_number": "+16195550142",
      "contact_name": "Jamie Rivera (Owner)",
      "last_message_status": "delivered"
    }
  ]
}

Changes

No recorded changes to this operation across all 2 revisions of this API.