Google Play Developer Reporting API

Name: Google Play Developer Reporting API API
Brand: Google Play Developer Reporting API
Availability: InStock

✓ Official Vendor SpecAnalyticsProduct Analyticsoauth27 EndpointsREST

For Agents

Query Android app vitals, error issues, and anomalies from Google Play Console for an app and any release filter.

Quickstart

Get started with Google Play Developer Reporting API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"query Android crash rate from Play Console"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google Play Developer Reporting API API.

Search apps by package name to confirm reporting access for a developer account

Query metric sets such as crash rate, ANR rate, slow-rendering rate, and excessive-wakeup rate

Fetch release filter options including app version, country, device type, and Android version

Search error issues to find the top crashes affecting an app's users

GET STARTED

Start building with Google Play Developer Reporting API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Google Play Developer Reporting API API for, with concrete tasks.

★ Release Health Dashboard

Build an internal dashboard that polls crash rate, ANR rate, and slow-rendering metrics per app version after every release. The metrics:query endpoint returns metric values broken down by dimensions like versionCode, countryCode, and deviceModel, and the anomalies list flags regressions automatically. Teams replace manual Play Console screenshotting with a continuously-refreshing release health view.

POST /v1beta1/{name}:query against the crashRateMetricSet with dimensions=['versionCode'], metrics=['crashRate'], and a 7-day timeline to chart crash rate per version.

Post-Release Regression Alerting

Wire Play's anomaly detection into the team's incident channel. The anomalies list endpoint returns anomalies the Play platform has detected on metric sets such as ANR rate or excessive wakeups, with the dimensions and time range affected. A scheduled job pulls new anomalies hourly and posts them to Slack with a deep link to Play Console for triage.

GET /v1beta1/{parent}/anomalies?filter=metricSet="crashRateMetricSet" and forward each new anomaly's dimensions and time range to Slack.

Top Crash Triage

Surface the top error issues affecting users so engineering can prioritise fixes. The errorIssues:search endpoint returns ranked error issues with sample stack traces, occurrence counts, and affected app versions. Exporting daily into a bug tracker lets teams treat the top 10 crashes as standing tickets without manual Play Console export.

GET /v1beta1/{parent}/errorIssues:search?pageSize=10&filter=type=CRASH and create a Jira ticket for each issue not already tracked.

AI Agent Vitals Querying via Jentic

Engineering agents that triage post-release health can call the Reporting API through Jentic without managing OAuth scopes or metric-set names directly. Jentic stores the developer's refresh token in its vault and exposes the right metricSet:query operation as a single search-load-execute call, turning a multi-day reporting integration into a same-day automation.

Search Jentic for 'query Android crash rate', load the metricSets.query schema, and execute it with the crashRateMetricSet name and a 14-day timeline.

Key Endpoints

7 endpoints — the google play developer reporting api gives android app developers programmatic access to the same vitals, errors, and anomaly data that appear in play console.

METHOD

PATH

DESCRIPTION

GET

/v1beta1/apps:search

Search apps the caller has access to

POST

/v1beta1/{name}:query

Query a metric set with dimensions, metrics, and a timeline

POST

/v1beta1/{name}:fetchReleaseFilterOptions

Fetch release filter options for a metric set

GET

/v1beta1/{parent}/errorIssues:search

Search top error issues for an app

GET

/v1beta1/{parent}/anomalies

List anomalies detected on metric sets

GET

/v1beta1/apps:search

Search apps the caller has access to

POST

/v1beta1/{name}:query

Query a metric set with dimensions, metrics, and a timeline

POST

/v1beta1/{name}:fetchReleaseFilterOptions

Fetch release filter options for a metric set

GET

/v1beta1/{parent}/errorIssues:search

Search top error issues for an app

GET

/v1beta1/{parent}/anomalies

List anomalies detected on metric sets

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Play Console service-account credentials are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access tokens at call time so the service account JSON never enters agent context.

Intent-based discovery

Agents search Jentic with intents like 'query Android crash rate' or 'list Android app anomalies' and receive the matching metric-set or anomalies operation with its full input schema.

Time to first call

Direct integration: 2-3 days for service account setup, scope linkage, and metric-set schema discovery. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Play Android Publisher API

Manage releases and listings whose health Reporting then measures

Choose Android Publisher to roll out a new release; use Reporting to measure its health afterwards.

Complementary

Google Play Integrity API

Attest device and app integrity at runtime alongside reporting on vitals

Choose Play Integrity for runtime trust signals; use Reporting for aggregated post-release vitals.

Complementary

Google Play Grouping API

Tag user segments inside an Android app for analysis alongside vitals data

Choose Play Grouping to tag users; use Reporting to query metric sets across all users.

FAQs

Specific to using Google Play Developer Reporting API API through Jentic.

What authentication does the Play Developer Reporting API use?

It uses OAuth 2.0 with the https://www.googleapis.com/auth/playdeveloperreporting scope and is typically called with a service account linked to the Play Console. Through Jentic the refresh token or service account credential is held in the Jentic vault and a scoped access token is injected at call time.

Can I get crash rate broken down by app version?

Yes. POST /v1beta1/{crashRateMetricSet}:query accepts a dimensions array including versionCode, countryCode, and deviceModel, plus a metrics array such as ['crashRate', 'distinctUsers']. Use fetchReleaseFilterOptions to discover which dimension values are valid for the selected app.

What are the rate limits for this API?

The API enforces standard Google Cloud project quotas measured in queries per minute. Metric queries are heavier than search calls, so dashboards that fan out across many metric sets in parallel may need a quota increase via Google Cloud Console.

How do I list anomalies through Jentic?

Run jentic search 'list Android app anomalies', load the schema for GET /v1beta1/{parent}/anomalies, and execute it with the app's parent resource name and an optional filter such as metricSet="crashRateMetricSet". Jentic handles OAuth automatically.

Is the Play Developer Reporting API free?

There is no per-call charge for the API itself, but it requires an active Google Play developer account and Google Cloud project. Standard quotas apply and metric queries are subject to reasonable-use limits.

Can I get sample stack traces for top crashes?

Yes. GET /v1beta1/{parent}/errorIssues:search returns ranked error issues with sample stack traces, occurrence counts, and the app versions affected, ranked by user impact. Use the issue's resource name to fetch deeper detail or to deep-link into Play Console.