linxio-js

Dashboard Source Analysis

Repeatable endpoint extraction from the Linxio dashboard JavaScript bundles.

The SDK includes maintainer tooling for analysing the Linxio dashboard bundles kept in sources/. The extractor scans JavaScript string and template literals, keeps path-like values used near HTTP method calls, normalizes dynamic template segments to {param}, and records the source bundle filenames where each candidate appeared.

pnpm analyze:sources

For machine-readable output:

pnpm analyze:sources -- --json

Current summary

The latest analysis run covered the ten JavaScript files currently checked into sources/.

MetricCount
Source files analysed10
Dashboard endpoint candidates extracted169
SDK endpoint catalogue definitions86
Dashboard candidates covered by the SDK catalogue56
Dashboard candidates not yet represented in the SDK catalogue113
SDK catalogue entries not observed in these dashboard bundles19

What the counts mean

dashboard candidates covered by the SDK catalogue means the same HTTP method and normalized path shape appears in both the extracted dashboard evidence and linxioEndpoints.

dashboard candidates not yet represented is not automatically a to-do list. Some candidates are admin-only, internal dashboard configuration, password/phone flows, chat/notification features, bulk import helpers, integrations, notes, or tenant-specific operational tools. They should be wrapped only after validating the payload shape and safety model.

SDK catalogue entries not observed can include public API endpoints, realtime channels, or endpoints documented elsewhere that are not directly present in the captured dashboard bundles.

Recently promoted wrappers

The current SDK catalogue includes dashboard-derived wrappers for area group lifecycle actions, device vendors, device installation rows, attached device cameras, vehicle counts, vehicle types, scheduled-report templates, scheduled report restore, read-only metadata and settings reference data, fuel types, and the dashboard-observed vehicle restore method.

High-signal dashboard-only candidates

These candidates are useful for future wrapper work because they are related to existing SDK domains and came directly from the captured dashboard bundles:

MethodsPathSource bundle
GET/notifications/event-typesmain.91cbbc5b3b642d22.js
GET/sensors/types4167.49eae6a246b4574d.js
POST/devices/{param}/notes4167.49eae6a246b4574d.js
POST/fuel-cards/upload5049.278d2bc7e646d60c.js

Use read-only validation first when turning any dashboard-only candidate into a public SDK method. Mutation wrappers should be added only when the payload, side effects, and rollback story are understood.

On this page