The LuLuMate Fleet API

Tokens

A fleet admin makes a token in Fleet → API: read only, or read and control. It's shown once; we keep only a fingerprint, and it can be revoked there at any time. Send it as a header:

Authorization: Bearer lmf_…

60 requests a minute per token (then 429 with Retry-After). Every call is logged and shown to the fleet's admins.

Calls

GET /api/fleet/v1/mowers

Every mower in the fleet: id, name, ble_name, site, status, online, state, battery, charging, lat, lon, last_mow, alerts. state is one of mowing, charging, paused, returning, idle, error, offline.

GET /api/fleet/v1/mowers/{id}

One mower.

POST /api/fleet/v1/mowers/{id}/dock

Send it back to its dock. Needs a read-and-control token.

POST /api/fleet/v1/mowers/{id}/pause

Pause what it is doing. Needs a read-and-control token.

POST /api/fleet/v1/mowers/{id}/resume

Carry on with the paused job. Needs a read-and-control token.

There is no "start mowing" call: a job is started in the mower's own LuLuMate, by a person.

Example

curl -H "Authorization: Bearer $TOKEN" https://lulumate.nz/api/fleet/v1/mowers
curl -X POST -H "Authorization: Bearer $TOKEN" https://lulumate.nz/api/fleet/v1/mowers/42/dock

Answers are JSON with ok; a refused call has error. Status is read from each mower's LuLuMate every few seconds; one that doesn't answer shows online: false.