Google Play

The googlePlay tag covers app details, availability, categories, category apps, data safety, developer listings, permissions, reviews, search, similar apps, and suggestions under /v1/googleplay/*. Follow the API Reference for each operation's id, country, language, pagination, and sorting parameters.

Choose an operation

Start with GET /v1/googleplay/search, which accepts term plus optional country, language, and limit. When you have a package identifier, GET /v1/googleplay/app_details/{id} reads one public detail record. That path also accepts country and language. Related reads include GET /v1/googleplay/similar_apps/{id}, GET /v1/googleplay/permissions/{id}, GET /v1/googleplay/availability/{id}, and GET /v1/googleplay/data_safety/{id}. Their path parameter is id; consult the contract for their optional parameters.

GET /v1/googleplay/reviews/{id} accepts country, language, limit, sort, score, and next_token. To inspect a publisher, use GET /v1/googleplay/developer with dev_id. Category discovery uses GET /v1/googleplay/categories, then GET /v1/googleplay/category_apps/{category}. GET /v1/googleplay/suggest accepts term. These are public-data reads, and the API Reference defines the returned schema for every endpoint.

Make a request

Store the API key outside source code and send it as a bearer credential. For example, search applications by term:

curl -sS \
  -H "Authorization: Bearer $REPLYNODES_API_KEY" \
  "https://api.replynodes.com/v1/googleplay/search?term=calendar"

Responses use the documented { data, meta } envelope, with meta.request_id for correlation. Read Quickstart for authentication handling, compare App Store, and use the API Reference for exact required fields and response schemas.

Use Google Play search or suggestions to discover an application before requesting details by its store identifier. Detail responses can be enriched with availability, category, data-safety, permission, review, developer, and similar-application operations. Country and language are not cosmetic values: they can affect which listing, release metadata, categories, or reviews are visible. Keep those parameters consistent when an agent compares several calls, and record them alongside the result so a later run can explain a changed answer. Category and developer routes are useful for building bounded research sets, but clients should still apply their own limit and pagination controls rather than attempting an unbounded crawl.

All operations in this guide are public, read-only lookups. They do not create reviews, change listings, or access private developer dashboards. The generated API Reference defines the exact path, parameter names, required identifiers, and response schema for the deployed contract. When a request fails, preserve the returned request_id, respect Retry-After for 429, and retry only safe transient reads with a finite backoff. Do not infer quotas, freshness, or retention promises that are not present in the runtime contract.