List support conversations

Every customer company’s Support channel, most recently active first. `status` is whose turn it is: `awaiting-reply` means a customer spoke last and we owe them an answer, `awaiting-customer` means we spoke last, `quiet` means nobody has written yet, `closed` means the channel is archived. `waitingOnUs` says the same thing as a boolean. `lastMessage` carries a preview and who wrote it, so a sweep of the queue needs no second read. Status is read off the last message, so a `status` filter is applied after the page is read: for a queue sweep, pass a wide `limit`. `search` matches the company’s name.

Required scope

The access token must carry this scope. A token missing it gets 403 Forbidden. Grant them to an API client under Dev Tools → API, to an assistant or CLI sign-in when you approve or edit it under Dev Tools, and to a teammate under Employee → Permissions.

internal:support:read

Query Parameters

Name	Type	Required	Description
`limit`	number	Optional	Maximum number of items to return (1-100).Default: `20`
`offset`	number	Optional	Number of items to skip before starting to collect the result set.Default: `0`
`sortBy`	string	Optional	Field to sort by. Allowed values vary by endpoint.Default: `createdAt`
`sortOrder`	string asc desc	Optional	Sort direction.Default: `desc`
`search`	string	Optional	Free-text search across the resource’s primary fields.
`createdAfter`	string	Optional	ISO 8601 timestamp — only return items created after this time.
`createdBefore`	string	Optional	ISO 8601 timestamp — only return items created before this time.
`updatedAfter`	string	Optional	ISO 8601 timestamp — only return items updated after this time.
`status`	string awaiting-reply awaiting-customer quiet closed	Optional	Whose turn it is.
`customerCompanyId`	string	Optional	One customer company’s channel.

GETExample request

curl

curl -X GET "https://www.pxb.app/api/public/v1/support-conversations" \
  -H "Authorization: Bearer your_access_token"

200Example response

json

{
  "message": "Support conversations retrieved successfully!",
  "content": {
    "supportConversations": [
      {
        "id": "cnv_7f21",
        "referenceId": 412,
        "channel": "threads",
        "status": "awaiting-reply",
        "waitingOnUs": true,
        "company": {
          "id": "cmp_a1b2",
          "name": "Northwind Traders"
        },
        "topic": "Your direct line to the Pixelbase team.",
        "lastMessage": {
          "id": "msg_5c90",
          "preview": "Our invoices stopped syncing to QuickBooks this morning — anything on your side?",
          "author": {
            "employeeId": "emp_9d1a",
            "name": "Priya Nair",
            "internal": false
          },
          "createdAt": "2026-10-09T14:12:00.000Z"
        },
        "lastMessageAt": "2026-10-09T14:12:00.000Z",
        "messageCount": 18,
        "memberCount": 4,
        "isArchived": false,
        "createdAt": "2026-03-02T10:00:00.000Z",
        "updatedAt": "2026-10-09T14:12:00.000Z"
      }
    ],
    "viewer": {
      "employeeId": "emp_12ab"
    },
    "pagination": {
      "total": 42,
      "limit": 20,
      "offset": 0,
      "hasMore": true
    }
  }
}

In the console

The same thing done by hand, for anyone comparing the API against the screen they already use.

Threads → Support

/threads