Skip to main content
Base URL: https://api.firmngin.dev/api/saas/v1/flash This collection covers the endpoints a third-party app, CLI, or local agent uses to resolve firmware, download a signed image, and record a local flash session. Any HTTP client can call these endpoints; the examples use a desktop app as the client.

Authentication

Workspace API key:
The ticket download endpoint uses the single-use ticket as its credential:
The workspace is derived from the API key. The key needs the Firmware update history (ota:read) scope. Optionally limit it to specific artifact codes in Dashboard → Integrations → Generate Token → Artifact codes.

Endpoints

List firmware

Only signed artifacts are returned. Use target_board and target_model to narrow the list.

Get a manifest

Returns 404 when the artifact is missing or outside the key’s artifact-code binding. Returns 409 when the latest artifact is unsigned.

Create a download

device_secret_id is optional. When present, Firmngin checks the firmware target against the device board and model.

Download firmware

The ticket is single-use and expires after five minutes. The response includes:
Verify X-Firmware-Sha256 and X-Firmware-Signature before flashing.

List devices

Use this to show the devices the workspace can flash.

Resolve a device

Use this to confirm the connected device’s board and model before downloading.

Read a session

The session records the ticket, firmware, optional device, nonce, and the advisory report.

Report a session

result is success or boot_failed. The nonce comes from POST /downloads.
This report is advisory. It does not update the device’s authoritative boot status or firmware version.

Errors

Flash via Third-Party overview

End-to-end flow and artifact-code binding.

Security model

Tickets, signature verification, temp files, and advisory reports.