Skip to main content
A package is a build of a game that Partner Center has received and processed. The package commands list and get a game’s packages, so you can check whether one is ready for a playtest. To upload a package, see Uploading packages. These commands are Experimental: their options and output might change. See Experimental commands. They need Partner Center’s Packages Read permission on the game, which the Developer role includes.

Commands

Arguments and options

The seller comes from --seller-id or your saved seller; see Context. Without one, the commands use your only seller, and ask for --seller-id when you belong to several. --xbox-title-id always needs a seller.

Listing packages

package list writes the ID of the game’s Main branch and a packages array with every field the service returns. package get writes one package in the same shape. An excerpt:
A package is ready for a playtest when all of these are true:
  • processingState is Processed. It moves from PendingUpload through Uploaded and Processing to Processed, or to ProcessFailed.
  • validationItems, the problems Partner Center found while processing the package, has no item with severity Error.
  • isAvailableForPlaytest is true.
--output table has PACKAGE ID, VERSION, PLATFORM, STATE, PLAYTEST, and CREATED columns. It doesn’t show validation results, so check validationItems in JSON.

Uploading packages

The CLI doesn’t upload packages. Upload them with makepkg from the XBOX Game Development Kit (GDK); see the makepkg reference, and for uploads from continuous integration (CI), Package Uploader. Then run package list to check that the package is ready.

Errors

Errors go to stderr as text, whatever --output is, with the correlation ID. --verbose adds the response body. A failure exits 1.

Examples

Last modified on November 18, 2026