Skip to main content

Support consistent `sortBy` / `updatedAt` sorting across all API v2 endpoints

General

Allow API v2 list and search endpoints (such as `POST /v2/conversations/search`) to support sorting by `updatedAt` / `recent` so developers can reliably fetch and poll for incrementally updated records.

Post type
💡 New feature
Posted by James Stevens ·
1 comment

Log in to comment and vote

Comments1

  • Martin Wood

    •

    Oct 6

    •

    Merged request

    •

    2 votes

    Support reliable incremental ticket extraction across linked conversation changes

    Ticket API responses include linked conversation data, but changes such as team reassignment do not advance the ticket’s updatedAt.
    Integrations using sortBy=recent can therefore miss updates and require costly full scans.

    Changes to ticket data exposed by the API should advance updatedAt and use the same timestamp for sorting and pagination.