Skip to content

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 forPollDetails
A salary to be paidGET /v03/api/calculations?$filter=status eq 'paymentStarted'Track the payment status
A payroll to closeGET /v03/api/payroll/{id} — info.statusPayroll lifecycle and statuses
Invoices for your payment channelinvoices with status unreadPayroll lifecycle → polling

Rules ​

  • Batch with list queries rather than one GET per object, and follow nextPageLink — 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 paymentStarted longer than your channel normally takes.

Every page is also available as Markdown: add .md to its URL — a folder page such as white-label/ is white-label/index.md. Index for LLMs: llms.txt. Questions: Support.