Appeeky covers both the Apple App Store (iOS) and Google Play (Android). Most store-intelligence endpoints accept a platform query parameter so you can pull the same metadata, keyword, and competitor data for either store.
platform defaults to apple, so existing iOS integrations keep working unchanged. Add platform=google to target Google Play.
| Value | Store | Notes |
|---|
apple (default) | Apple App Store | Aliases: app-store, ios, iphone |
google | Google Play | Aliases: play, google-play, android |
# Apple (default)
curl "https://api.appeeky.com/v1/keywords/metrics?keyword=music&country=us" \
-H "X-API-Key: YOUR_API_KEY"
# Google Play
curl "https://api.appeeky.com/v1/keywords/metrics?platform=google&keyword=music&country=us" \
-H "X-API-Key: YOUR_API_KEY"
App identifiers differ by store
| Platform | Identifier | Example |
|---|
apple | Numeric App ID (iTunes track ID) | 1617391485 |
google | Package name | com.spotify.music |
:id validate it against the selected platform. Passing a numeric ID with platform=google (or a package name with platform=apple) returns INVALID_APP_ID.
The lang parameter (Google Play)
Google Play localizes content by language as well as country. Pass an optional lang (e.g. en, tr, de) on Google requests; it defaults to en. lang is ignored for Apple, which derives language from the storefront country.
curl "https://api.appeeky.com/v1/apps/com.spotify.music?platform=google&country=de&lang=de" \
-H "X-API-Key: YOUR_API_KEY"
country parameter uses ISO 3166-1 alpha-2 codes for both stores.
These accept platform=apple or platform=google:
| Group | Endpoints |
|---|
| Search | GET /v1/search |
| Apps | GET /v1/apps/:id, /intelligence, /similar, /reviews, /country-rankings, /keywords, /keywords/trends |
| Keywords | GET /v1/keywords/ranks, /suggestions, /metrics, /compare, /compare-cluster, /trending, POST /v1/keywords/track |
| Screenshots | GET /v1/apps/:id/screenshots, /screenshots/competitors, GET /v1/categories/:id/top/screenshots |
| Categories | GET /v1/categories/:id/top |
| ASO | GET /v1/aso/apps/:id/audit, /opportunities |
Apple-only endpoints
These rely on Apple-specific data sources or accounts and accept iOS apps only:
- App Store Connect — your apps, versions, metadata, analytics, sales reports, reviews (Apple developer account)
- Apple Search Ads — campaign management (Apple Ads account)
- AI Visibility — AI-assistant recommendation tracking
- Advanced keyword insights —
keywords/visibility, keywords/movers, keywords/gap, keywords/demand-trend, keywords/suggestions/history, keywords/suggestions/emerging, apps/:id/keyword-clusters, keywords/expand
- ASO —
aso/.../brief, intent clusters, metadata suggest/validate, competitor report
Google Play coverage for the advanced keyword-insight endpoints is on the roadmap. Until then, those endpoints return data for Apple apps only.
Notes on Google Play metrics
- Volume, difficulty, and opportunity scores are computed from Google Play-native signals (search results, ratings, review counts, autocomplete) using the same scoring core as Apple, so values are comparable across stores.
- Enrichment fields (
rankVolatility, marketDominance, historicalDays) are currently populated for Apple only. On Google these return null and interpretation.trustworthy is false until enough historical rank data accumulates.
