Repository navigation
Interfaces and API
Zachary Nathan Goode edited this page Oct 4, 2026
·
1 revision
The firmware advertises _filelink._tcp.local. using mDNS. The Windows client discovers that service and communicates with the device over plain HTTP. HTTPS is not implemented in the supplied code.
| Group | Endpoints |
|---|---|
| Device |
/api/info, /api/identify, /api/device/name, /api/device/time, /api/device/factory_reset
|
| Network/auth |
/api/settings/network_fallback, /api/auth/status, /api/auth/verify, /api/auth/set_password, /api/wifi/config, /api/wifi/scan
|
| SD |
/api/sd/status, /api/sd/list, /api/sd/download, /api/sd/upload, /api/sd/delete, /api/sd/mkdir, /api/sd/format, /api/sd/benchmark
|
| RS232 |
/api/rs232/status, /api/rs232/configure, /api/rs232/write, /api/rs232/read
|
| OTA | /api/ota/update |
Requests/status responses are JSON-oriented except streaming file/firmware bodies and raw RS232 traffic. Downloads include X-File-CRC32 when cache data is ready; uploads provide CRC32 in the request URL.
The firmware directly checks the configured password for password-management and factory-reset operations. Ordinary SD, RS232, OTA, Wi-Fi, identify, and device-information handlers do not show global password middleware. This limitation is intentional documentation, not an inference. See Security Boundaries.