Google Play V2

Save Google Play Configuration

Changed on

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

Request

  • Base URL
    https://api.superwall.com
  • URL
    https://api.superwall.com/v2/projects/{id}/applications/{application_id}/integrations/google-play/configuration
  • Auth
    • HTTP bearer
    • or API key in cookie accounts_superwall_token
    • or HTTP bearer

Path parameters

idstring required
application_idstring required

Request body

package_namestring required

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

service_account_jsonstring

Full contents of the downloaded Google Cloud service-account JSON key file. Stored sealed at rest and never returned

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

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • warning

      added the new credentials_missing enum value to the / response property for the response status

    • info

      added subschema #1 subschema #2 subschema #3 subschema #4 subschema #5 to the response body anyOf list for the response status

    • info

      removed subschema #1 subschema #2 subschema #3 subschema #4 subschema #5 from the response body anyOf list for the response status

    • breaking

      the request property type changed from boolean to no type

    • breaking

      the request property type changed from string to no type

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from number to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    • breaking

      the response's property type changed from string to no type for status

    This list may be incomplete.