Upload API

Request a signed URL

One endpoint, two aliases. Both paths do the same thing, and the legacy path exists so older clients keep working.

POST https://<upload-worker>/api/storage/presign-upload
POST https://<upload-worker>/upload-url            (alias)
Authorization: Bearer <studio token>
Content-Type: application/json

{
  "type": "game-build",              // game-build | game-web | app-file | app-media
  "fileName": "my-game-1.4.0.zip",   // sanitised to [\w.-], 140 chars
  "gameId": "my-game",               // required for game-* types
  "appId": "my-game",                // required for app-* types
  "version": "1.4.0",                // defaults to "draft", else Date.now()
  "size": 734003200,                 // bytes, must be > 0
  "contentType": "application/zip",  // optional, capped at 120 chars
  "contentEncoding": "gzip"          // optional
}

200 {
  "uploadUrl":   "<presigned PUT, valid 10800s>",
  "fileUrl":     "https://storage.appsinity.com/public/games/my-game/builds/1.4.0/my-game-1.4.0.zip",
  "key":         "games/my-game/builds/1.4.0/my-game-1.4.0.zip",
  "objectKey":   "same as key",
  "bucket":      "public",
  "contentType": "application/zip",
  "contentEncoding": "",
  "expiresIn":   10800
}

Object key layout

The validation gates

Every rule below is enforced by the service, after the sanitisers have already run on your name. The client repeats several of them for a faster message, and the service decides.

blocked (16): .php .exe .sh .bat .cmd .ps1 .msi .dmg
            .jar .com .scr .vbs .app .xapk .ipa .rar
allowed (13): .apk .aab .zip .html .js .wasm .data
            .json .png .jpg .jpeg .webp .mp4

caps: game-build 5 GiB | game-web 5 GiB | app-file 5 GiB
      app-media 250 MiB
current object key sanitiser: NFKD, keep [\w.-], collapse runs,
                              trim, slice to 140

Sending the bytes

1. PUT to uploadUrl. Use the URL exactly as returned, including its query signature. Any edit invalidates it.
2. Match Content-Type. Send the returned contentType verbatim; a mismatch is a failed signature check.
3. Send the body raw. No multipart envelope and no wrapping field.
4. Do not exceed three hours. A large upload on a slow connection can outlive the URL; the gate is total elapsed time, not transfer time.
5. Record fileUrl. That is the value your listing's build or web URL must take, including /public/.
6. Re-request on failure. A new presign is cheap; a retried PUT against an expired URL never succeeds.

Confirming an object exists

• No credential is required for this call, because it returns metadata about an object in a public bucket.
• Only the public bucket is accepted; anything else is Invalid bucket.
• The check is a HEAD, so it tells you size and type but nothing about contents.
• Use it after an upload to confirm the object landed with the byte count you sent.

POST https://<upload-worker>/api/storage/file-info
{ "bucket": "public", "key": "games/my-game/builds/1.4.0/my-game-1.4.0.zip" }

200 {
  "bucket": "public",
  "key": "games/...",
  "sizeBytes": 734003200,
  "sizeFormatted": "700.00 MB",
  "contentType": "application/zip",
  "contentEncoding": ""
}

400 { "error": "File info lookup failed (404)." }