Cross-manufacturer robotic mower diagnostic API

Endpoint

POST /.netlify/functions/diagnostic-api-v1
x-api-key: YOUR_KEY
content-type: application/json

The endpoint also accepts an active Owner/Workshop browser session for first-party use.

Request

{
  "brand": "Segway Navimow",
  "model": "X430",
  "code": "6106",
  "symptom": "Stops in an open area; manual control still works"
}

Response shape

{
  "ok": true,
  "mode": "knowledge-and-observed-data",
  "matches": [{
    "rank": 1,
    "confidenceIndex": 88,
    "title": "Motion Planning Error",
    "category": "Navigation / motion planning",
    "verification": "manufacturer-exact",
    "steps": ["..."],
    "sourceUrl": "..."
  }],
  "disclaimer": "Confidence index ranks knowledge-base relevance..."
}

Important: the relevance index is a search/diagnostic ranking signal. It is not a measured component-failure probability.

Authentication

Commercial API clients use keys supplied through the MOWERFIX_DIAGNOSTIC_API_KEYS server environment variable. Keys are never embedded in browser code. First-party workshop sessions can call the endpoint using secure session cookies.

Future connector interface

The API schema separates knowledge from observed/connected mower data. Future manufacturer, Bluetooth, Wi‑Fi or fleet connectors can supply telemetry without changing the diagnostic record format.

{
  "observations": {
    "batteryPercent": 71,
    "rtkStatus": "single",
    "stationLed": "green",
    "source": "connector:mammotion"
  }
}