Get affiliate statistics and referrals

One ordered stream of the things that already reach the dashboard bell: a service provisioned or suspended, an invoice raised, a charge that failed. **This is what to poll** instead of diffing `/v1/services` and `/v1/invoices` against your own copy. Two cursors, and they walk opposite ways: - `before` — page back through history, newest first. - `after` — everything since id N, **oldest first**. That ordering is the point: newest-first, a client that missed more than `limit` rows would advance its cursor past what it never read. `nextCursor` is always passed back in the same parameter you used. Rows can be deleted (the dashboard bell dismisses them), so ids in the feed can have gaps. Read-only: nothing here marks a notification read — `read` is the dashboard's state.