Method: edits.expansionfiles.upload

  • This page details how to upload a new expansion file and attach it to a specified APK.

  • Two types of HTTP POST requests are available for this action: a media upload URI and a metadata URI.

  • The request and response bodies are described, including the JSON representation of the successful response.

  • Authorization requires the https://www.googleapis.com/auth/androidpublisher OAuth scope.

Uploads a new expansion file and attaches to the specified APK.

HTTP request

  • Upload URI, for media upload requests:
    POST https://androidpublisher.googleapis.com/upload/androidpublisher/v3/applications/{packageName}/edits/{editId}/apks/{apkVersionCode}/expansionFiles/{expansionFileType}
  • Metadata URI, for metadata-only requests:
    POST https://androidpublisher.googleapis.com/androidpublisher/v3/applications/{packageName}/edits/{editId}/apks/{apkVersionCode}/expansionFiles/{expansionFileType}

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
packageName

string

Package name of the app.
editId

string

Identifier of the edit.
apkVersionCode

integer

The version code of the APK whose expansion file configuration is being read or modified.
expansionFileType

enum (ExpansionFileType)

The file type of the expansion file configuration which is being updated.

Request body

The request body contains an instance of ExpansionFilesUploadRequestBody.

Response body

Response for uploading an expansion file.

If successful, the response body contains data with the following structure:

JSON representation 
{
  "expansionFile": {
    object (ExpansionFile)
  }
}
Fields
expansionFile

object (ExpansionFile)

The uploaded expansion file configuration.

Authorization scopes

Requires the following OAuth scope:

  • https://www.googleapis.com/auth/androidpublisher