HTTP SpecEndpoints
List bundles
GET /bundles returns the bundles a remote currently has deployed, optionally scoped to a channel.
Return the bundles a remote currently has deployed. The client and updater call this first to discover which bundles exist and what version each is deployed at, before reading metadata or downloading bytes.
GET /bundlesParameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
channel | query | string | No | Select a channel's deployments. When omitted, the default deployment is listed. |
Responses
| Status | Description |
|---|---|
200 | A JSON array of the currently deployed bundles. |
For 4xx responses, see Errors.
Response headers
| Header | Required | Description |
|---|---|---|
Content-Type | Yes | application/json for the list response. |
Response body
The body is a JSON array. Each item describes one deployed bundle by name and version. Bundles that are not deployed are excluded.
[
{ "name": string, "version": string }
]| Field | Type | Description |
|---|---|---|
name | string | The bundle name. |
version | string | The currently deployed version. |
Example
curl -s http://localhost:4313/bundlesHTTP/1.1 200 OK
Content-Type: application/json
[
{ "name": "app", "version": "1.2.0" },
{ "name": "admin", "version": "0.4.1" }
]Scope the list to a channel with ?channel=:
curl -s 'http://localhost:4313/bundles?channel=beta'This operation is the entry point of the remote HTTP contract. To read a bundle's current metadata or download its bytes, see the Remote HTTP Spec overview.