Submit an Update

The following is an example of the sequence of Content Publish APIs used to create an app update, upload a new binary, and submit the app.

1. POST /seller/createUploadSessionId

   Create a session ID to upload the new binary.

   
   

2. POST /galaxyapi/fileUpload

   Upload the new binary and get a file key.

   
   

3. GET /seller/contentInfo?contentId=XXXXXXXXXXXX

   Get the app information of the binary that is for sale (the appStatus is SALE). The information in the response can be modified in the next step.

   NoteIf you want to copy the device configuration (the devices a binary is targeting) from an existing binary to the new binary, save the binarySeq value from the existing binary from which you want to copy the device configuration. This value is used when you add a new binary (see step 5).

4. POST /seller/contentUpdate

   Create an update for the app (the appStatus of the update is REGISTRATION). After calling this API, the app has two appStatus statuses (SALE and REGISTRATION). See Status Parameters for more information about the appStatus parameter. You will add the binary for the update in the next step.

   During this step, you should make any required metatdata changes as well as any adjustments to the countries where the app is to be distributed.

   
   

5. POST /seller/v2/content/binary?contentID=XXXXXXXXXXXX&gms=Y/N&filekey=xxxxxxxxx&binarySeqForDeviceInfo=X

   Register the binary you uploaded in step 2 and copy the device configuration (if desired) from an existing binary based on the binarySeq value you noted in step 3.

   
   

6. (Optional) POST /seller/v2/content/binary?contentId=XXXXXXXXXXXX&binarySeq=X

   Delete a previously registered binary. This makes the binary completely inaccessible through Galaxy Store.

   
   

7. POST /seller/contentSubmit

   Submit the app for review.
   

   NoteIf the publicationType of the app is set to manual publication, the app does not go live after it has passed the review. There will be an app pending release whose appStatus is REGISTRATION. This app can be released using POST /seller/contentStatusUpdate.