Webhooks and change tracking

The QUiCK API does not send webhooks — there is no event subscription and no callback endpoint. You track changes by polling: you periodically query the list endpoints and process whatever was created or modified since your last sync.

The expense list can be filtered and ordered by date, which makes it easy to fetch everything created since a given moment. date_field selects which date field to filter on, from_date sets the starting date and ordering controls the order:

curl "https://api.quick.riport.co.hu/1/expenses/?date_field=created&from_date=2026-07-01&ordering=-created&page_size=100" \
  -H "Authorization: Token $QUICK_API_TOKEN"

The response is paginated (count / next / previous / results); follow the next URL to collect every new item.

Incomes are filtered the same way with from_date:

curl "https://api.quick.riport.co.hu/1/incomes/?from_date=2026-07-01&page_size=100" \
  -H "Authorization: Token $QUICK_API_TOKEN"

The current balance of cash and bank accounts comes from GET /1/pulse/ — you can poll this more often than the full expense list, because it returns a single lightweight response.

• Store the timestamp of the last successful sync and pass it as from_date on the next run.
• Use a small overlap (for example a from_date one day earlier) so items on the boundary are not missed; de-duplicate by id.
• Do not poll too frequently. Tight polling loads the API for no benefit; most accounting integrations are fine with a minute-to-hour cadence. Too many requests will return 429 Too Many Requests.