Push Firmware Update (OTA)

Pushes a firmware image to the device over the local network to perform an
over-the-air update. The device verifies the package, flashes it, and reboots
automatically on success.

Firmware package format depends on the device model. The accepted
extension is one of .bin, .tar, or .zip — the caller is expected to
fetch the correct package for the target device (typically resolved from
screen_model / board_model returned by /deviceInfo) and upload it as-is.
Do not transcode or repack.

ExtensionTypical usage
.binSingle-image firmware (legacy / smaller boards).
.tarMulti-partition bundle (newer boards with separate assets).
.zipCompressed bundle (boards that ship resources alongside fw).

Request: multipart/form-data with a single part named update
containing the firmware bytes. The filename in the multipart part
should carry the correct extension (e.g. firmware.bin, firmware.tar,
firmware.zip) so the device can dispatch the right handler.

Recommended client timeouts: send ≥ 2 minutes (large packages over
Wi-Fi), receive ≥ 30 seconds (device responds after verification, before
reboot).

Behavior: the device returns {"status": "ok"} after the package is
accepted and staged. The actual flash + reboot happens immediately after
the response; the device will be unreachable for a short window during reboot.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
file
required

Firmware package binary. The multipart filename must end with .bin, .tar, or .zip matching the target device.

Responses

400

Rejected — malformed package, unsupported extension, or signature/version mismatch.

500

Internal error while writing the package to flash.

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json