Appearance
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 |
| A payroll to close | GET /v03/api/payroll/{id} — info.status | Payroll lifecycle and statuses |
| Invoices for your payment channel | invoices with status unread | Payroll lifecycle → polling |
Rules
- Batch with list queries rather than one
GETper object, and follownextPageLink— see Queries and paging. - 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
paymentStartedlonger than your channel normally takes.

