Upload and verify a signed Tilecast Player release bundle
const url = 'https://example.com/api/v1/player-releases/upload';const form = new FormData();form.append('files', 'file');
const options = {method: 'POST'};
options.body = form;
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/v1/player-releases/upload \ --header 'Content-Type: multipart/form-data' \ --form files=@fileAccepts one release’s three files as multipart files: the artifact, the signed update manifest and its signature. The file names select the family: tilecast-player.apk with tilecast-player-update.json (Android), tilecast-player.AppImage with tilecast-player-update-linux.json (Electron Linux), or tilecast-edge-<version>-<arch>.tar.zst with the signed envelope tilecast-edge-update.json (Tilecast Edge). Owner session plus CSRF or a configured release-publishing bearer token is required.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Responses
Section titled “ Responses ”Release fully verified and cached
object
object
The Player release family. A deployment reaches only screens of its release’s family, and for edge only screens of its architecture.
x86_64 or aarch64 for Tilecast Edge; empty for the other families.
The artifact size
Example
{ "data": { "platform": "android", "playerFamily": "android", "source": "upload", "channel": "stable" }}Invalid publishing token
Upload exceeds configured limits
Missing file or verification failure