Stop polling for load and trip status. Subscribe to webhook events.

What’s new

React to load and trip transitions in real time. Two new webhook events are live: load.status.changed and trip.status.changed. Alvys emits a webhook the moment a load or trip changes status. Each payload carries the previous status, the new status, and the full Public-API load or trip snapshot.

Why it matters

• Unlock integrations that weren't viable before. Teams that needed real-time visibility into Alvys but couldn't justify the cost, latency, and operational overhead of building it themselves can now subscribe and start receiving updates in seconds — no scheduler, no backoff logic, no reconciliation jobs to maintain.
• Modernize existing integrations. Replace polling loops with push delivery. Status changes reach your TMS, factoring, and visibility systems the moment they happen, not on the next poll cycle.
• Cut wasted API traffic. Stop hitting /loads and /trips for changes that haven't happened. Lower request volume, fewer rate-limit headaches, less reconciliation drift.
• Trigger logic on specific transitions. previousStatus ships in every payload, so you can branch on the exact transition (e.g. Dispatched → InTransit) without maintaining your own state machine.
• Audit every delivery. Each attempt is logged on the Webhook details page — payload, response, retry history

How to use it

1. Open Settings → API → Webhooks.
2. Create or edit a webhook subscription.
3. Select load.status.changed, trip.status.changed, or both.
4. Save the subscription.
5. Confirm delivery in your webhook delivery logs.

Pull the full event list from GET /p/v1.0/webhooks/event-types.

Behavior notes

• Events fire only on real transitions. Same-status updates do not trigger.
• Inherit the same delivery pipeline as tender.* events. Signing, retries, delivery logs, and auto-disable behave identically.
• The load or trip snapshot may be null on oversized payloads. The status delta is always present.