Cases and the change feed

How to find out what moved, without webhooks.

This platform has no webhooks, so nothing will call you. GET /cases is the mechanism that replaces them: it is ordered by when each case last changed, so one request tells you everything that has moved since you last looked.

Walking the feed

• Call GET /cases?changedSince=... with the time you last caught up.
• Process the page, then follow nextCursor until hasMore is false.
• Store the cursor. The next page starts exactly where the last one ended, whatever has been written in between.

curl 'https://api.example.com/api/v1/integration/cases?changedSince=2026-10-13T00:00:00Z' \
  -H "X-API-Key: pmt_live_..."

The feed is wider than your own traffic

It includes cases no session of yours created: a customer who came through a link the institution sent, a re-verification, a case staff opened. If you are reconciling the institution's book rather than only your own requests, that is what you want. A case with no sessionId simply arrived another way.

How often to poll

Every few seconds while you are waiting on something specific, and every minute or so otherwise, is comfortable within the published rate limits. Back off on 429 and respect Retry-After.