Sign in
Google Play V2

Save Google Play Configuration

Validates the service-account key and package name against Google and, only when every check passes, persists them with the key sealed at rest. When a check fails the response is { valid: false, saved: false, checks } and the stored configuration is left untouched. Set configure_pubsub to also create the default notifications topic and the Superwall push subscription in the same call. Requires applications:write scope.

put/v2/projects/{id}/applications/{application_id}/integrations/google-play/configuration

Path parameters

idstring required

Project ID

Project ID

application_idstring required

Application ID

Application ID

Request body

package_namestring required

Android package name (application ID), e.g. com.acme.app

service_account_jsonstring

Key to validate and store. Omit to change only the package name, re-validating against the key already stored

configure_pubsubboolean

When true, also create the default notifications topic (with the Google Play publisher binding) and the Superwall push subscription in the same call. Defaults to false so a stepped setup flow can drive those explicitly

Response

Success

object'google_play_configuration_save_result' required

Object type, always google_play_configuration_save_result

validboolean required

True when no check failed. Warnings do not make the result invalid

errorstring nullable required

Message from the first failing check, for callers that only want one line

failed_check'key_format' | 'credentials' | 'androidpublisher_api' | 'package_access' | 'pubsub_api' | 'pubsub_topic' | 'pubsub_subscription' nullable required

Which check failed first; null when valid

savedboolean required

Whether the configuration was persisted. False whenever a check failed

Changes

No recorded changes to this endpoint across all 1 revision of this API.