Skip to main content
GET
List Matters changed since a timestamp

Authorizations

Authorization
string
header
required

Environment-specific Integration key. Never paste a live key into documentation tooling.

Query Parameters

clientCode
string
required

Granted Local Authority Client code

Pattern: ^[A-Z][A-Z0-9]{1,31}$
Example:

"SDCC"

updatedSince
string<date-time>
required

Inclusive UTC lower bound. Use the syncedThrough value from the last fully applied run, or the initial boundary agreed at onboarding. A future instant returns 400 invalid_field.

pageToken
string
limit
integer
default:100
Required range: 1 <= x <= 200

Response

Page of changed Matters

matters
object[]
required
nextPageToken
string | null
required

Opaque continuation token; null on the final page.

syncedThrough
string<date-time> | null
required

The UTC instant this run is guaranteed to have covered, and the value to send as the next run's updatedSince. It is null on every page except the final one, so a run abandoned part-way cannot advance a caller's saved boundary: save it only after every page has been applied.

It is held a short interval behind the run's snapshot boundary so it never reports coverage through a window in which writes may still be committing, and it is never earlier than the requested updatedSince. It is returned on the final page even when no Matter matched, which is what makes an empty run advance safely. Treat the exact lag as a server detail that may change; do not reimplement it or add an overlap of your own.

Example:

"2026-09-21T01:58:00Z"