Webhooks

RushHour does not offer webhooks. There is no way to register a URL that RushHour calls when an order, route, invoice or other record changes.

To keep another system up to date, your integration needs to ask the API for changes on a schedule.

Checking for changes on a schedule

There is no "changed since" filter

List filters work on business values — for example an order's or a route's date, or a status — not on when a record was last changed. A request for this week's orders does not include an older order that someone edited today, and a request for this month's invoices does not include last month's invoice that was paid today.

1. Choose an interval that matches how fresh the data must be — every few minutes for dispatch data, hourly or daily for accounting exports.
2. Decide which records can still change. Work out the set your integration cares about that is still open — for example orders that are not finished yet, or invoices that are not fully paid — and the business-date period those records fall in.
3. Re-read that whole set on every run. Use the filters an endpoint offers, such as statuses or a date range, to request it, and page through all the results — see Pagination and filtering. Don't narrow the request to "recent" dates only, or you will miss edits to older records.
4. Compare by ID. Match each record with the copy you already have, and update what differs. A record you had before that no longer appears may have been deleted, or may no longer match your filters — check it on its own before you remove it.
5. Handle date boundaries. If you split the period into several date windows, overlap them slightly and remove duplicates by ID — see Dates and time zones.
6. Back off on errors. If you get 429 or 503, wait before the next attempt — see Rate limits.

Notifications for people

The notifications RushHour shows in its applications, and the emails it sends, are meant for your team, your customers and your drivers. They are not designed as a way to feed other software.