Status Parameters

Many of the Galaxy Store Developer APIs require you to use the app's contentID and the app's status to identify the app/content you would like to modify.

The contentID is a 12-digit identifier that is created when you register an app in Seller Portal and can be found when you go to the Apps tab in Seller Portal.

There are two different status parameters, contentStatus and appStatus, that are used to help identify an app and indicate an app's status throughout the application process. Below is a description of these two status parameters as well as a table mapping the status values to the status displayed in Seller Portal.

appStatus

The Galaxy Store Developer APIs typically use the appStatus parameter to refer to the application status and help identify the app. appStatus is not displayed in Seller Portal.

There are only two values for appStatus and it is possible for content in Seller Portal to have either or both of these statuses at the same time:

REGISTRATION
SALE

TipYou can call the /seller/v2/content/stagedRolloutBinary/ API endpoint with appStatus=REGISTRATION and appStatus=SALE to check to see if there's an app for the content with that status. A response with a failure code of 3100 ("Not found for contentId") indicates that the content doesn't currently have an app with the requested appStatus.

The table in the Status parameters mapping section at the bottom of this page maps the status displayed in Seller Portal to the appStatus value.

REGISTRATION only

The Colorful Moment app has been registered in Seller Portal but has not been submitted for review and is not publicly accessible to users in Galaxy Store. In Seller Portal, the status of the app is displayed as "Registering."

For app content that displays "Registering" as their status in Seller Portal, any Galaxy Store Developer APIs that require the appStatus parameter should use REGISTRATION when modifying this content.

SALE only

The Driving Game app has been registered in Seller Portal, submitted for review, passed the review, and is accessible to users in Galaxy Store. In the example shown above, there have not been any updates created for the app.

For app content that displays "For Sale" as their status in Seller Portal, any Galaxy Store Developer APIs that require the appStatus parameter should use SALE when modifying this content.

REGISTRATION and SALE

The Simple Digital Watch app has been registered in Seller Portal, submitted for review, passed the review, and is accessible to users in Galaxy Store. An update has been created for this content either after clicking Update in Seller Portal or calling the /seller/contentUpdate API endpoint. This content has two possible appStatus values: SALE refers to the version of the app that is published in Galaxy Store and available to users (the status displayed in Seller Portal for this app is "For Sale") and REGISTRATION refers to the version of the app that is being updated (the status displayed in Seller Portal for this app is "Updating").

The appStatus value that you use depends on the version of the app you want to modify. If you want to modify the app that is for sale, you would use SALE. If you want to modify the app that is being updated, you would use REGISTRATION.

contentStatus

While appStatus only considers two possible states of an app, contentStatus shows where the app is in terms of the Galaxy Store review and release process and mostly matches what is displayed in Seller Portal. For example, the Colorful Moment app in Seller Portal displays the status of "Registering" and the contentStatus for this app is REGISTERING (indicating the app has not been submitted for review). For the Simple Digital Watch app, Seller Portal displays the status of "Updating" and the contentStatus for this app is UPDATING (indicating the app is an update to a submitted app). Note that both of these apps have the same appStatus value (REGISTRATION).

The Key Tool app has been registered in Seller Portal, configured for manual publication, submitted for review, passed the review, and is ready for publication.

For app content that displays "Ready for Change" as their status in Seller Portal, any Galaxy Store Developer APIs that require the contentStatus parameter should use READY_FOR_CHANGE when modifying this content. The appStatus of this app is REGISTRATION.

The table in the Status parameters mapping section below maps the status displayed in Seller Portal to the contentStatus value.