Skip to main content
GET
Platform release selection: service firmware must be explicitly released for your authenticated project in the platform, as well as published in OTA. Available but unselected, stopped, superseded or upstream-withdrawn versions are not eligible for new public requests. See Firmware Updates.
Model-based service releases add optional release_sequence and allow_downgrade. For one device/model, prefer the highest released sequence; semantic version alone does not represent an authorized rollback. Hardware revision is not required. Release IDs remain organization-scoped fw_* references. Bota builds and publishes firmware; you choose which release a device runs. This returns the releases selected for your authenticated project, newest first. Pass device_id to narrow the list to what that device can install. Without it you get selected releases for the models in your project scope. Unpublished releases are never returned. A release that is still being prepared has a placeholder checksum and may have no uploaded image behind it, so there is nothing you could safely install from it.

Authentication

Requires an API key with devices:read scope.

Query Parameters

string
Return only releases this device can install (e.g., dev_abc123). The device must belong to the project your key is scoped to, otherwise the request is a 404.

Response Fields

Notes

  • Artifact references remain organization-scoped. Release selection is per project; a sibling project selecting the same reference does not authorize this project.
  • The list is newest-first. Do not infer “latest” from the version string — a rollback publishes an older version as the newest release.