Build Uploads

WebGL build structure

The zip must contain index.html and a *.loader.js file:

your-build.zip
├── index.html          ← required
├── Build/
│   ├── game.loader.js  ← required
│   ├── game.wasm
│   ├── game.data
│   └── game.framework.js
└── TemplateData/

A single wrapping folder is fine — if Unity exports to WebGLBuild/, the upload strips that prefix for you. What fails is a zip with several top-level folders and no index.html inside any single one. __MACOSX/ and ._ entries created by macOS are ignored automatically.

Missing either index.html or a *.loader.js file is rejected with Invalid build: missing index.html or loader file.

Archive limits

Limit	Value
Files in the archive	1,000
Single file, uncompressed	200 MB
Whole archive, uncompressed	1.5 GB

These are checked before extraction, so an oversized build fails fast rather than part-way.

Upload via Developer Portal

Developer Portal → your game → Builds → Upload Build
Select platform (WebGL, iOS, Android)
Set version ID — use semantic versioning (1.0.0) or dates (2026-08-01)
Add release notes — describe what changed and how to test
Upload zip

Upload via CI/CD

Your pipeline uses the same three steps the portal uses, authenticated with your developer API key. The zip goes straight to storage, so its size is not limited by the API.

1. Ask for a signed upload URL

UPLOAD_URL=$(curl -sS -X POST https://api.susaplay.com/catalog/get-upload-url \
  -H "Authorization: ApiKey $DEVELOPER_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"gameId\":\"$GAME_ID\",\"versionId\":\"$VERSION\",\"platform\":\"webgl\"}" \
  | jq -r '.data.uploadUrl')

The URL is valid for 20 minutes. This call fails early if the version already exists or you are at the review cap, so you find out before uploading anything.

2. Upload the zip

curl -sS -X PUT "$UPLOAD_URL" \
  -H "Content-Type: application/zip" \
  --upload-file ./dist/game.zip

3. Register the build

curl -sS -X POST https://api.susaplay.com/catalog/process-build \
  -H "Authorization: ApiKey $DEVELOPER_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"gameId\":\"$GAME_ID\",\"versionId\":\"$VERSION\",\"platform\":\"webgl\",\"notes\":\"Build $CI_COMMIT_SHA\"}"

SusaPlay validates the archive, extracts it, and creates the version in pending_review.

The old single-call POST /catalog/publish endpoint has been removed. It sent the zip in the request body, which caps at 32 MiB — smaller than most WebGL builds. Move any pipeline still calling it to the three steps above.

Remote content ships separately — see Addressables for updating levels or art without a new build.

Build retention

SusaPlay keeps a limited number of builds per platform and deletes older ones automatically, along with their files.

Rule	Value
Builds kept per platform	5 most recent
Grace period before a build can be removed	24 hours
Builds you can have in review at once	3

Never deleted automatically: the live build, a build waiting for review, and anything uploaded within the grace period. Subscribe to the BUILD_PRUNED webhook if your pipeline needs to know when a version was removed. Uploading past the review cap is rejected with 409 until one of your pending builds is reviewed or deleted, so ask for a review rather than queueing more builds.

Version states

State	Meaning
`pending_review`	Submitted, awaiting review
`live`	Currently served to players
`deprecated`	Replaced by a newer live version
`rejected`	Failed review — fix issues and resubmit

A passing review moves a version straight to live. There is no separate approved-but-not-live state.

Release notes checklist

Good release notes help reviewers pass builds faster:

What changed since last version
Known issues or workarounds
Test account credentials if auth is required
Which platforms were tested

Getting Started

Integration

SDK

API

WebGL build structure

Archive limits

Upload via Developer Portal

Upload via CI/CD

1. Ask for a signed upload URL

2. Upload the zip

3. Register the build

Build retention

Version states

Release notes checklist

​WebGL build structure

​Archive limits

​Upload via Developer Portal

​Upload via CI/CD

​1. Ask for a signed upload URL

​2. Upload the zip

​3. Register the build

​Build retention

​Version states

​Release notes checklist

WebGL build structure

Archive limits

Upload via Developer Portal

Upload via CI/CD

1. Ask for a signed upload URL

2. Upload the zip

3. Register the build

Build retention

Version states

Release notes checklist