Read the submission state
get_submission_stateWhether the game can be submitted to moderation now and, if not, why — the first rule the submit itself would refuse with. reason, in that order: ORGANIZATION_BANNED, MODERATION_UNAVAILABLE (the game cannot go to moderation, catalogAvailable is false: publish it to the sandbox), missing certification, a cooldown after a failed moderation, the state of the build being submitted (ARCHIVE_PENDING, ARCHIVE_FAILED, ARCHIVE_CHECKING while its check is still running, or the archive’s own reason code — get_archive_status explains it), ARCHIVE_NOT_BUILDABLE (the build has no Bridge version or Bridge config to build with: integrate the Bridge SDK and upload it again), FORM_INCOMPLETE (details names the fields to fill or fix, the title included: empty or with non-Latin letters), COVERS_INCOMPLETE (not all three covers are in place: upload the ones emptySlots names), or nothing changed since the last submit. message is the console’s wording of that refusal. Name in archiveId the build you are asking about — the one a submit would freeze. While catalogAvailable is false the answer is always MODERATION_UNAVAILABLE, whatever the build: never tell the developer the game can be submitted. A game never submitted to moderation, or one moderation rejected or postponed, whose sandbox is not blocked (get_sandbox_state), opens once its sandbox reaches the targets shown on its sandbox card in the console — the play time among them is set by the game’s category — counted once a day. A game moderation took off, or whose sandbox is blocked, only Playgama can reopen: the sandbox targets do not. A game Playgama restricted stays closed whatever its targets and track, until Playgama lifts the restriction. A human submits to moderation in the console. With reviewType AUTO the verdict is send_playgama_catalog_update’s: the same reasons, then AUTO_REVIEW_UNAVAILABLE — the game is not live in the Playgama catalog (autoReviewPlatforms is empty), so only moderation can take it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"applicationId": "<applicationId>",
"archiveId": "<archiveId>"
},
"name": "get_submission_state"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| archiveId | Yes | The build this answer judges — the archive a submit would name. get_application and get_launch_steps answer the archives of the game; an archive of another game is refused | |
| reviewType | No | Optional. MANUAL (left out): judge a submit to moderation, which a human sends from the console. AUTO: judge send_playgama_catalog_update — an update of the game live in the Playgama catalog without moderation | |
| applicationId | Yes | Game id from list_applications |