Connect work order feeds, subscribe to signed webhooks for bay events, and automate technician notification sequences.
Initialize the Lanekeeper client and dispatch your first work order to Bay 1.
curl -X POST https://api.lanekeeper.io/v1/jobs/dispatch \
-H "Authorization: Bearer lk_live_99248a129ef0" \
-H "Content-Type: application/json" \
-d '{"bay_id":"bay_01","vehicle":"2023 Toyota RAV4"}'
Every API request requires a Bearer token in the Authorization header. You can generate production keys (lk_live_...) and sandbox keys (lk_test_...) in the Lanekeeper App settings.
Lanekeeper sends signed HTTPS POST payloads when schedule state changes on the shop floor. All webhook payloads include an HMAC-SHA256 signature in the X-Lanekeeper-Signature header.
Fires the moment a job drifts beyond the configured tolerance window (default: 10 minutes past estimated pace).
Fires when a technician toggles bay status (e.g. OCCUPIED, WAITING_PARTS, QUALITY_CHECK, IDLE).
Fires when an automated customer notification or delay alert is confirmed delivered by the carrier network.
Install our open-source client libraries with built-in TypeScript types and webhook verification helpers.
npm install @lanekeeper/sdkpip install lanekeeper