EDIT: ignore this, looks like they're rolling out some sorta revamped notification system so let's hold off until that's out fully?
Looks like the /notifications/list endpoint uses the query parameter before with a datetime for pagination now, and offset no longer seems to affect the returned results. I think it's been this way for a while.
Under the new scheme the request looks something like:
GET /api/v1/notifications/list?limit=40&before=2024-02-27T12:30:39.968Z
EDIT: ignore this, looks like they're rolling out some sorta revamped notification system so let's hold off until that's out fully?
Looks like the
/notifications/list
endpoint uses the query parameterbefore
with a datetime for pagination now, andoffset
no longer seems to affect the returned results. I think it's been this way for a while.Under the new scheme the request looks something like:
GET /api/v1/notifications/list?limit=40&before=2024-02-27T12:30:39.968Z
and the API response would look something like:
I can have a stab at making the necessary code changes if you'd like? It would mean a minor API break for scripts using the library...