Google Play APIs
Collect public Google Play app details, category rankings, and reviews from known store URLs as normalized app and review records.
Available Google Play APIs
Use App Detail for known listings, App Rankings for public chart URLs, and App Reviews for public feedback from known app URLs.
What Google Play data can you retrieve?
The normalized app schema keeps public listing fields nullable instead of replacing missing source values with assumptions.
App identity and copy
Retrieve package ID, app name, public description, developer, category, and source URL when available.
Visible listing signals
Keep available rating, review count, install range, price, and rank as point-in-time store observations.
Media and collection context
Preserve media fields and collected_at with the normalized app record.
Google Play API contract overview
Each endpoint starts from known public Google Play URLs and returns normalized records through the asynchronous task workflow.
| Endpoint | Input | Source scope |
|---|---|---|
| App Detail | Non-empty array of app URLs | At most one app record per accepted URL |
| App Rankings | Category or ranking URLs and optional results_limit | Apps exposed by the submitted charts |
| App Reviews | App URLs with optional country and results_limit | Public reviews for the submitted apps |
How the Google Play APIs work
All three endpoints use the standard asynchronous task workflow.
1. Submit known URLs
Choose the matching endpoint, POST its required urls array and optional controls, and retain task_id.
2. Track the task
Poll /v1/tasks/{task_id} until processing succeeds or fails.
3. Read stored records
Read data.results.items after success and follow next_cursor only when SocQ has another stored-result page.
Authenticate with a SocQ API key and submit known public Google Play app URLs.
curl -X POST "https://api.socq.ai/v1/google-play/app-detail" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://play.google.com/store/apps/details?id=com.openai.chatgpt"]}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.itemsCommon Google Play API use cases
Application catalog enrichment
Add normalized identity, public listing copy, developer, category, and source context to known app links.
Selected listing comparison
Compare available public price, rating, review, install, and media fields across a controlled URL set.
Point-in-time observation
Retain repeated records with collected_at to compare nullable public listing fields over time.
Limits and public-data policy
Results depend on current public listing visibility and expose no account-management or publishing functions.
- Every input item must resolve to play.google.com or one of its subdomains.
- The APIs do not accept keywords or package IDs alone; supported optional fields depend on the selected endpoint.
- App Detail can return at most one record per URL, while Rankings and Reviews use a task-wide results_limit from 1 to 2,000.
- Task-result cursors paginate records already stored by SocQ, not additional Google Play pages.
- Final billing is 0.15 credits per stored result with no base charge; estimates use URL count for App Detail and the requested or default result limit for Rankings and Reviews.
Google Play API frequently asked questions
What is the Google Play API?
The Google Play APIs retrieve app details, collect category rankings, and collect public app reviews from known Google Play URLs.
Can I send multiple app URLs?
Yes. Submit a non-empty array of strings, each using the play.google.com host or a supported subdomain.
Can the APIs discover apps?
App Rankings discovers apps exposed by submitted chart URLs; the APIs do not provide keyword search.
How are results charged?
Each stored result costs 0.15 SocQ credits. Final charges use actual result count; estimation depends on the selected endpoint.
Combine data across platforms for more complete business insights
Bring public profiles, content, and engagement data from different platforms into one workflow to track brands, creators, and topics and run cross-platform monitoring and analysis more efficiently.
Kwai API
Retrieve public Kwai profiles, one page of account posts, or one known post with normalized identity, content, media, timestamps, and visible engagement.
Truth Social API
Retrieve public account details, collect one source page of account posts, or resolve one known post URL into normalized records.
LinkedIn API
Retrieve public LinkedIn profile, company, post, and job data from known URLs, with normalized identity, career, company, content, engagement, and job fields.
Reddit API
Retrieve public Reddit posts and comments from known URLs, browse new, top, or hot subreddit posts, or search discussions by keyword and publication window.
Rednote API
Retrieve public profiles and notes, search notes or users, collect comments and nested replies, and capture one home recommendation page.
Pinterest API
Retrieve public Pinterest profile data, resolve known Pins, collect Pins from selected profiles, or search by keyword for creator, content, and visual trend research.