Upload and verify a signed Tilecast Player release bundle

POST

/api/v1/player-releases/upload

curl --request POST \
  --url https://example.com/api/v1/player-releases/upload \
  --header 'Content-Type: multipart/form-data' \
  --form files=@file

Accepts 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), or tilecast-windows-<version>-<arch>.msix with the signed envelope tilecast-windows-update.json (Windows Player). Owner session plus CSRF or a configured release-publishing bearer token is required.

Request Body^required

Media typemultipart/form-data

object

files

required

Array<string>

>= 3 items <= 3 items

Responses

201

Release fully verified and cached

Media typeapplication/json

object

data

object

id

string format: uuid

platform

string

playerFamily

The Player release family. A deployment reaches only screens of its release’s family, and for edge and windows only screens of its architecture. The set grows with new players; clients must tolerate values they do not recognize.

string

architecture

x86_64 or aarch64 for Tilecast Edge and Windows Player; empty for the other families.

string

source

Allowed values: upload github

versionCode

integer

versionName

string

channel

Allowed values: stable beta

apkSizeBytes

The artifact size, for every family.

integer

duplicate

boolean

Example

{
  "data": {
    "source": "upload",
    "channel": "stable"
  }
}

401

Invalid publishing token

413

Upload exceeds configured limits

422

Missing file or verification failure