Appearance
Google Play API
All paths begin with /api/v1/orgs/:orgId/apps/:appId/google-play. Configuration routes require a dashboard session. Publication routes also accept an app-matched API token with the listed scope.
| Method and suffix | Minimum access | Success |
|---|---|---|
GET / | Viewer session | 200 configuration view |
PUT / | Admin session | 200 configuration view |
DELETE / | Admin session | 204 |
POST /verify | Admin session | 200 verification result |
GET /publications | Viewer session or read token | 200 { "items": [...] } |
POST /publications | Developer session or promote token | 202 queued publication |
PATCH /publications/:id | Developer session or promote token | 202 queued update |
POST /sync | Developer session or promote token | 200 { "items": [...] } |
PUT / accepts packageName, optional defaultLanguage (default en-US), and service-account JSON text in serviceAccountJson. The service-account credential is write-only and may be omitted when updating an existing configuration. The view exposes configured, packageName, serviceAccountEmail, defaultLanguage, and lastVerifiedAt.
GET /publications?releaseId=rel_... filters the list. POST /publications accepts releaseId, optional artifactId, track, percent (1–100, default 100), and includeNotes (default true). Standard tracks are internal, alpha, beta, and production; a valid custom closed-track name is also allowed. A PATCH accepts either { "percent": 50 } or { "action": "halt" }, { "action": "resume" }, or { "action": "complete" }. Publication objects include track, version code, status, rollout fraction, busy flag, error, and sync timestamps. POST /sync queries Google Play immediately; an upstream sync failure can return 502 play_request_failed.
Store actions queue work, so 202 means accepted rather than published. Check the publication status after processing. Invalid JSON fields produce route-validation 400 responses; an app outside the organization is hidden with 404.