Overview

Any server that implements this HTTP contract can act as a remote. The providers implement it for you; read this only when you build your own.

A client reads bundles in three steps:

1. GET /bundles — list the deployed bundles.
2. HEAD /bundles/{name} — read the current version's metadata to check for an update.
3. GET /bundles/{name} — download the current version's bytes. GET /bundles/{name}/{version} downloads an exact version.

Metadata headers

Bundle responses carry metadata in Webview-Bundle-* headers, not the body. Webview-Bundle-Name and Webview-Bundle-Version are required — the client rejects a response missing either. Webview-Bundle-Integrity and Webview-Bundle-Signature are optional. Bundle bytes are served as application/webview-bundle.

Channels

A channel selects a separate deployment track. The list, metadata, and current-download routes accept an optional ?channel= query; omit it to target the default deployment. The exact-version route takes no channel.

Endpoints

For non-2xx responses, see Errors.