Documented steps

POST .../applications/{packageName}/edits (edits.insert) and capture editId.
GET .../edits/{editId}/listings/{language} (edits.listings.get) to read the current Listing for that BCP-47 language, e.g. en-US or de-AT.
Build a Listing body: {"language":"en-US","title":"...","shortDescription":"...","fullDescription":"..."}. The optional video field takes a promotional YouTube URL.
PUT .../edits/{editId}/listings/{language} (edits.listings.update) to replace the localized listing, or use edits.listings.patch to change a subset of fields.
Example: curl -X PUT -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' -d '{"language":"en-US","title":"My App","shortDescription":"Short pitch","fullDescription":"Full description"}' "https://androidpublisher.googleapis.com/androidpublisher/v3/applications/$PKG/edits/$EDIT_ID/listings/en-US"
Repeat per language you support. Listings are stored per language, not merged.
For release notes, GET .../edits/{editId}/tracks/{track} (edits.tracks.get) to fetch the Track and its releases array.
Modify the target release's releaseNotes array, adding a LocalizedText {"language":"en-US","text":"What's new"} per locale.
PUT .../edits/{editId}/tracks/{track} (or edits.tracks.patch for a partial change) to persist the release notes.
POST .../edits/{editId}:commit and read the response for validation errors before assuming the listing went through.

Known gotchas

Play Console documents these listing limits: app title 30 characters, short description 80 characters, full description 4000 characters. The API reference itself does not restate them, so over-length text typically surfaces as a validation error at commit rather than at update.
language must be a valid BCP-47 tag your app supports. Unrecognized language codes are ignored rather than erroring.
No character limit for releaseNotes text is documented in the tracks reference; do not assert one.
Release notes live on the Release inside a Track, not on the Listing. Updating a listing does not change what users see as 'What's new'.
tracks.update is a full PUT replace; fetch the track first or use patch.
Listing edits require an open uncommitted edit, and any concurrent Play Console UI change discards it.
Official docs: https://developers.google.com/android-publisher/api-ref/rest/v3/edits.listings/update , https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks , https://support.google.com/googleplay/android-developer/answer/9859152

developers.google.com/android-publisher · 10 steps · unrated

Promote an existing Google Play release from one track to another without re-uploading the binary by reusing its versionCodes

developers.google.com/android-publisher · 9 steps · unrated

Write localized App Store metadata (description, keywords, promotional text, what's new, URLs) plus app name and subtitle via the App Store Connect API

developer.apple.com/documentation/appstoreconnectapi · 14 steps · unrated

Give your agent this knowledge — and 16,200+ more routes

One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Update a localized Google Play store listing (title, short and full description) and a track release's localized release notes

Documented steps

Known gotchas

Related routes

Give your agent this knowledge — and 16,200+ more routes

Need this verified for your stack — or a route we don't have yet?