# Events and polling

**There are no webhooks or push notifications today.** Your integration learns about changes by **polling** the read endpoints.

That is enough for payroll: status changes follow banking-day events, not seconds. Polling every few minutes is plenty.

## What to poll

| You are waiting for | Poll | Details |
|---|---|---|
| A salary to be paid | `GET /v03/api/calculations?$filter=status eq 'paymentStarted'` | [Track the payment status](https://code.salaxy.com/get-started/rest/track-status.md) |
| A payroll to close | `GET /v03/api/payroll/{id}` — `info.status` | [Payroll lifecycle and statuses](https://code.salaxy.com/integration/payroll-lifecycle.md) |
| Invoices for your payment channel | invoices with status `unread` | [Payroll lifecycle → polling](https://code.salaxy.com/integration/payroll-lifecycle.md#what-this-means-for-polling) |

## Rules

- **Batch with list queries** rather than one `GET` per object, and follow `nextPageLink` — see [Queries and paging](https://code.salaxy.com/reference/queries.md).
- **Stop polling an object once its status is final.**
- **A quiet object is not a stuck one** — Salaxy never times a payment or an invoice out. Alert on your own expected processing time.
- **Keep polling after the salary month closes**: tax and union invoices appear on day 6 of the following month.

## Checklist

- One list query per interval, not one call per calculation.
- Final statuses stop the polling for that object.
- An alert fires when a payment stays `paymentStarted` longer than your channel normally takes.
