curl --request POST \
--url https://patch.gg/api/v1/projects/{owner}/{slug}/releases/{version}/submit \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://patch.gg/api/v1/projects/{owner}/{slug}/releases/{version}/submit', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://patch.gg/api/v1/projects/{owner}/{slug}/releases/{version}/submit"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"project": "<string>",
"version": "<string>",
"channel": "dev",
"status": "draft",
"kind": "web_game",
"trust_tier": "sandboxed",
"changelog": "<string>",
"recipe": {},
"manifest": {},
"created_at": "<string>",
"submitted_at": "<string>",
"published_at": "<string>"
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}Check the uploads and files, then start the release's review
Runs the file checks. A browser game then waits for a test on its creator’s PC (POST …/tests); a mod goes to the cloud review and then to a staff member. Staff keys publish directly. Follow it with GET …/review.
curl --request POST \
--url https://patch.gg/api/v1/projects/{owner}/{slug}/releases/{version}/submit \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://patch.gg/api/v1/projects/{owner}/{slug}/releases/{version}/submit', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://patch.gg/api/v1/projects/{owner}/{slug}/releases/{version}/submit"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"project": "<string>",
"version": "<string>",
"channel": "dev",
"status": "draft",
"kind": "web_game",
"trust_tier": "sandboxed",
"changelog": "<string>",
"recipe": {},
"manifest": {},
"created_at": "<string>",
"submitted_at": "<string>",
"published_at": "<string>"
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}{
"error": {
"code": "version_exists",
"message": "<string>",
"details": "<unknown>"
}
}Authorizations
An API key (pch_...) or the token from pch login.
Path Parameters
"patch"
"demo-mod"
"0.1.0"
Response
The submitted release
dev, private, unlisted, public draft, then checking (file checks). A browser game is testing until a test on its creator's PC passes, then cloud_review, then published. A mod goes to cloud_review, then in_review (a staff member), then published. Any step can end in rejected.
draft, checking, testing, cloud_review, in_review, published, rejected, yanked, quarantined web_game, mod, crossover_mod, remix What the release can do on the player's PC, worked out from its recipe and files: runs sandboxed in Patch, changes game files only, or runs code. Drives the consent sheet and review.
sandboxed, game_files_only, runs_code The release's recipe with its defaults filled in (https://patch.gg/schemas/recipe/v1.json). Null for releases made before recipes.
Show child attributes
Show child attributes
Deprecated: the patch.json of releases made before recipes, else null.
Show child attributes
Show child attributes