---
title: "Get Google Play Configuration"
method: GET
path: "/v2/projects/{id}/applications/{application_id}/integrations/google-play/configuration"
tags: ["Google Play V2"]
---

# Get Google Play Configuration

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

Returns the application's stored Google Play configuration. Never echoes key material — only safe descriptors such as the service-account email and Google Cloud project. An application with no configuration returns `configured: false` rather than a 404, so callers can distinguish 'not set up' from 'set up but broken'. Requires applications:read scope.

## Path parameters

- `id` string, required — Project ID
- `application_id` string, required — Application ID

## Response `200`

Success

- object
  - `object` 'google_play_configuration', required — Object type, always `google_play_configuration`
  - `configured` boolean, required — Whether the application has a stored Google Play configuration at all
  - `package_name` string, nullable, required — Android package name (application ID) the credentials are scoped to
  - `has_service_account_key` boolean, required — Whether a sealed service-account key is stored
  - `service_account_email` string, nullable, required — `client_email` from the stored key — the address to invite in the Play Console
  - `project_id` string, nullable, required — Google Cloud project the service account belongs to
  - `pubsub_topic_name` string, nullable, required — Fully qualified Pub/Sub topic receiving Real-Time Developer Notifications
  - `pubsub_subscription_id` string, nullable, required — Fully qualified Pub/Sub push subscription delivering notifications to Superwall
  - `push_endpoint` string, nullable, required — Superwall ingestion URL for this application's notifications. Paste into the Play Console when configuring RTDNs manually
  - `created_at` string, nullable, required — ISO 8601 timestamp of when the configuration was first saved
  - `updated_at` string, nullable, required — ISO 8601 timestamp of the last configuration change

## Other responses

- `400` — The request did not match the expected schema
- `401` — No API key was provided in the request
- `403` — The API key does not have permission to perform this action
- `404` — The requested resource was not found
- `429` — Too many requests have been made in a short period
- `500` — An unexpected error occurred on the server

---

[API](https://skmtc.dev/superwall/apis/superwall-api-v2.md) · [All operations](https://skmtc.dev/superwall/apis/superwall-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/superwall/superwall-api-v2/revisions/44900ad77d2c/schema)