Read work order state, subscribe to signed webhooks for bay events, and drive your own notification sequences.
Create the client, then dispatch your first work order into 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 request carries a bearer token. Production keys start with lk_live_ and sandbox keys with lk_test_. Both are generated in the console under settings.
Authorization: Bearer lk_live_your_api_secret_key
Lanekeeper posts signed payloads when schedule state changes on the floor. Every payload carries an HMAC-SHA256 signature in the X-Lanekeeper-Signature header.
job.slipping_alert high priority Fires the moment a job drifts past the tolerance window you configured. Ten minutes by default.
bay.status_changed state Fires when a technician moves a bay between occupied, waiting on parts, quality check and idle.
customer.sms_delivered gateway log Fires when the carrier confirms a status update or delay notice reached the customer.
Typed clients with webhook verification helpers built in.
npm install @lanekeeper/sdkpip install lanekeeper