{"id":14418,"date":"2026-09-24T10:29:36","date_gmt":"2026-09-24T10:29:36","guid":{"rendered":"https:\/\/playgama.com\/blog\/?p=14418"},"modified":"2026-09-24T10:29:36","modified_gmt":"2026-09-24T10:29:36","slug":"how-to-automate-web-game-uploads-using-portal-apis-and-cli-t","status":"publish","type":"post","link":"https:\/\/playgama.com\/blog\/business-faqs\/how-to-automate-web-game-uploads-using-portal-apis-and-cli-t\/","title":{"rendered":"How to automate web game uploads using portal APIs and CLI tools?"},"content":{"rendered":"

Automate web game uploads by scripting your engine export, compression, and verification steps in CI, then uploading via developer consoles since major web game portals do not offer public REST APIs or CLI tools for direct automated uploads. You can fully automate building the deployable zip package, leaving only the final portal console upload step manual.<\/strong><\/p>\n

At a glance<\/h2>\n\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
Portal uploads are done via web console<\/td>\nnot public REST APIs<\/td>\ndevelopers.poki.com<\/a><\/td>\n<\/tr>\n
itch.io hosts HTML5 builds in an iframe<\/td>\non its own domain<\/td>\nitch.io<\/a><\/td>\n<\/tr>\n
Web export engines produce a static build folder<\/td>\nUnity, Godot, Construct, etc.<\/td>\ndocs.unity3d.com<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

There is no universal CLI or API across portals for uploading a finished web build – Poki, CrazyGames, GameDistribution, and itch.io all take the build (usually a zip of your HTML5\/WebGL export) through a web developer console, not a public upload endpoint. What you can automate is everything before that step: your engine’s export\/build command, zipping the output, running checks (build size, console errors), and versioning – wired into a CI script that produces a ready-to-drop zip each time you push code.<\/p>\n

Where to publish once the build is ready<\/h2>\n