AppTweak’s App Store API returns app store optimization (ASO) and app-store data through a set of REST endpoints, each returning one type of data: keyword volumes, rankings, app reviews, app downloads and revenue estimates, top charts, and metadata.
Most teams do not need unlimited access to AppTweak’s API. They need the two or three endpoints behind one specific job: keyword volumes across iOS and Android, a competitor’s rank history, a clean feed of reviews, or download and revenue estimates for a market. Starting from the data rather than the endpoint list is faster, and it is how teams wiring app-store data into business intelligence (BI) tools and AI assistants reach a working integration.
AppTweak’s App Store API gives developers and data teams direct access to one of the industry’s largest app-store databases: 17 million+ keywords, 6 million apps, and historical data across 100+ countries since 2014.
Key takeaways
- AppTweak’s App Store API returns app store optimization (ASO) and app-store data through REST endpoints grouped by capability, covering the App Store and Google Play in 100+ countries with history since 2014
- Each endpoint returns one type of data, so the fastest way to build is to match a data need to its endpoint rather than reading the whole API
- Keyword volumes, rankings, app reviews, app downloads and revenue estimates, top charts, metadata, and ad-intelligence data each have dedicated endpoints across iOS and Android
- The API is complementary to the official Apple and Google APIs, adding market, competitive, and historical data those APIs do not expose
- Access uses an API key and is metered in credits, and the same data and credits are available through AppTweak’s remote MCP server for AI assistants
- App reviews are available as structured data through documented endpoints, a supported alternative to scraping store pages
Who is the AppTweak App Store API for?
The AppTweak App Store API is built for developers, data teams, and tech-savvy marketers who want app store data inside their own tools rather than in a dashboard. Typical users include:
- engineers and product teams building internal ASO tools or commercial products on app store data
- data teams piping rankings, keyword, and market data into a warehouse or BI stack
- agencies pulling data at scale across many clients and markets
- marketers and analysts working in AI assistants like Claude or Cursor who want to query the data
If your work mostly happens inside a visual ASO platform, AppTweak already covers that. The API is for teams that want the same data programmatically.
How to leverage AppTweak’s API to power your ASO workflows?
Each endpoint returns one type of data; the value comes from combining them. Two use-cases show up most often.
Powering your own tools and products with ASO and keyword data. Product and data teams pull keyword volumes, difficulty, suggestions, and rankings from the Keyword Metrics and Keyword Suggestions endpoints to feed their own applications: internal ASO tools, client-facing dashboards, or commercial products built on app store data. Called on a schedule, across a full keyword set and competitors’ in every market, the endpoints keep that data current with no manual pulls. One consistent schema across the App Store and Google Play means a single integration serves iOS and Android. Start from the Keyword Metrics reference.
Feeding rankings and metrics into a BI dashboard. Data teams pull rankings, download and revenue estimates, and category metrics into their own warehouse, then model them alongside internal data such as spend, retention, and revenue in the BI tool the business already uses. The App Store API is built to be queried this way. One consistent schema across both stores means the same pipeline handles iOS and Android without special-casing, which is the most common reason data teams adopt the API.
What data does each AppTweak API endpoint return?
Each row below maps a data need to the endpoint that serves it. Use it to find your entry point, then follow the documentation link for parameters and request syntax.
| Capability | Endpoint(s) | Stores / device | Countries | Typical use-case | Docs |
|---|---|---|---|---|---|
| Keyword volumes and difficulty | Keyword Metrics – Current / History | iPhone, iPad, Android | 100+ | Keyword research and prioritization | keyword-metrics-current |
| Keyword suggestions | Keyword Suggestions – App / Category / Volume growth / Trending | iOS, Android | 100+ | Discovering new keywords | keyword-suggestions-app |
| Rankings and search-results history | App Keyword Ranking – Current / History; Keyword Live Search | iPhone, iPad, Android | 100+ | Tracking rank and visibility | app-keyword-ranking-history |
| Top charts and category rankings | Top Charts – Current / History; App Category Ranking; DNA Charts | iOS, Android | 100+ | Market and category monitoring | top-charts-current |
| Download and revenue estimates | App Metrics – Current / History; Category Metrics | iPhone, iPad, Android | 100+ | Benchmarking and market sizing | app-metrics-current |
| Reviews and ratings | App Reviews – Search / Displayed / Stats | App Store, Google Play | 100+ | Voice-of-customer analysis at scale | app-reviews-search |
| App metadata and details | App Metadata – Current / History; Twin App; Featured Content; In-App Events | App Store, Google Play | 100+ | Metadata and competitor monitoring | app-metadata-current |
| Paid-search and ad intelligence data | App Paid Keywords; Keywords Share of Voice | iPhone, iPad, Android | 100+ | Seeing which apps bid on a keyword and their share of voice | app-paid-keywords |
| Query from an AI assistant (MCP) | Remote MCP server, over the same API and credits | iOS, Android | 100+ | Asking for data in plain language from an AI editor | mcp |
| Your own connected accounts | Integrations: App Store Connect and Google Play Console reports | iOS, Android | — | Blending first-party analytics with market data | account-list |
Notes on the data these endpoints return
- AppTweak returns two keyword volume metrics. The Keyword Metrics endpoints return both. Search Popularity is Apple’s official score (scale 5–100), but the App Store now groups many lower-demand keywords into its lowest tier, so a Search Popularity of 5 reflects how the store classifies a keyword, not how many people actually search for it. To fix that, AppTweak added a Volume Estimate — a proprietary figure built from historical data and market signals that recovers more representative volumes for those keywords, and it is now the default. On the endpoints, the volume field returns the Volume Estimate and search_popularity returns Apple’s raw score. See how AppTweak calculates keyword volume and the Keyword Metrics reference.
- App reviews are the compliant route. The App Reviews endpoints return store reviews filtered by term, rating, or reply status, as structured data through a documented API. For teams currently scraping review pages, this is the supported alternative: reviews at scale without maintaining brittle scrapers against store HTML.
- Historical depth is the differentiator. The app metadata, ranking, and keyword endpoints carry history back to 2014. Point-in-time data you can get in several places. A decade of consistent history across 100+ countries is far rarer, and it is what makes trend analysis and backtesting possible with AppTweak.
Every endpoint above is part of AppTweak’s App Store API, one schema across the App Store and Google Play.
How do you authenticate and manage API credits?
You authenticate with an API key passed in the request header, and every call draws from a credit balance. There are no per-seat licenses to manage. You provision a key, and usage is metered by the volume and type of data you request.
Three things are worth understanding before you build:
- Credits, not calls. Cost is tied to the data returned, so a broad historical query costs more than a single current lookup. You can check your remaining balance programmatically with the credits usage endpoint, which makes it straightforward to monitor spend inside your own pipeline.
- Start with one request. The getting-started walkthrough takes you through a first authenticated call, so you can confirm your key and see the response shape before writing any integration code.
- Plans and pricing. The API is available across pricing tiers with a free trial to test against real data. Because plan details change, check the current pricing overview and the pricing reference rather than hard-coding assumptions about allowances.
Rate limits and credit costs vary by endpoint and plan, so the reference documentation for each endpoint is the source of truth for what a given call will consume.
What are the limitations of AppTweak’s App Store API?
Being clear about the edges is more useful than implying the API does everything. As of this writing, a few limits are worth knowing.
- It is read-only. The API returns data. It does not take actions or change anything in your AppTweak account or in the stores.
- It does not expose your own paid-campaign performance. Competitive ad-intelligence data, meaning which apps bid on a keyword and their share of voice, is available as market data. Your own campaign performance from the ad platforms is not surfaced through this API.
- Some in-platform data lives only in the platform. A few datasets exposed in the AppTweak web platform, for example mobile measurement partner (MMP) connections, are not available through the API.
Conclusion
The practical way to approach AppTweak’s App Store API is to start from the data you need, not the endpoint list. Find your capability in the table above, whether that is keyword volumes, rankings, reviews, downloads and revenue, top charts, metadata, ad-intelligence data, or MCP access, follow the documentation link, and make a first authenticated call before you design the full integration. Start from the API documentation and a free trial, then scale into automated research, BI pipelines, or AI-assistant workflows.
FAQs
What data can you get from a third-party app store API?
A third-party app store API gives you market-wide app store data that the official Apple and Google APIs do not expose: keyword, ranking, competitive, and historical data across millions of apps. Data categories available through AppTweak’s App Store API include:
- keyword volumes, difficulty, and suggestions across iOS and Android
- app rankings, live search results, and top charts
- app download and revenue estimates, per app and per category
- app reviews and ratings as structured data
- app metadata, featurings, and in-app events
- paid-search and ad-intelligence data, such as which apps bid on a keyword and their share of voice
Coverage spans 100+ countries with history back to 2014, and the same data is reachable through the REST API or AppTweak’s remote MCP server.
What are ASO API endpoints?
An ASO API endpoint is a specific REST URL that returns one type of app-store data: keyword metrics, rankings, reviews, downloads, metadata, and so on. You call it over HTTPS, pass parameters like the app ID, country, and device, and get structured JSON back. Usage is metered in credits rather than per seat, so cost scales with what you actually query.
Endpoints are grouped by capability. That grouping is a useful mental model, because you rarely need “the API” as a whole. You need the two or three endpoints that answer your question. The rest of this page is organized that way.
One framing point worth stating plainly. AppTweak’s App Store API is complementary to the official Apple and Google APIs, not a replacement for them. Apple’s App Store Connect API and the Google Play Developer API give you first-party access to your own apps. AppTweak adds what those APIs do not: market-wide, competitive, and historical data across millions of apps and keywords, in one consistent schema across both stores. Most teams use both, the platform APIs for their own account and AppTweak for the market around it.
Which AppTweak API endpoint returns app rankings?
AppTweak’s App Keyword Ranking endpoints (Current and History) return an app’s rank for a given keyword, and the Top Charts and App Category Ranking endpoints return category and chart positions. Choose by the question you are answering: keyword-level rank and its history come from App Keyword Ranking, while category standing and chart movement come from Top Charts, App Category Ranking, and DNA Charts. All cover iPhone, iPad, and Android across 100+ countries. To see which apps rank for a term on the live search results page, use the Keyword Live Search endpoint instead. For request parameters and response fields, follow each endpoint’s reference documentation.
Which API supports bulk keyword research across iOS and Android?
AppTweak’s App Store API supports bulk keyword research across both iOS and Android through its Keyword Metrics and Keyword Suggestions endpoints. Keyword Metrics returns volume, difficulty, and related metrics for the keywords you submit; Keyword Suggestions surfaces new keywords by app, by category, by volume growth, and by trend. Because the API uses one consistent schema across the App Store and Google Play, the same request pattern works for both stores, so you can research a full keyword set in every market you operate in without special-casing each platform. Note that on 11 August 2026 the volume field began returning AppTweak’s Volume Estimate, with a separate search_popularity field for the raw score.
Is there a compliant alternative to scraping app reviews?
Yes, a documented app store data API is the compliant alternative to scraping: it returns app store reviews as structured data, so you never parse store HTML. Instead of scraping review pages, you request reviews through an API endpoint and get them back filtered by term, rating, or reply status across the App Store and Google Play. This is more reliable than scraping, because you are not maintaining parsers against changing store markup, and it delivers reviews at the scale needed for voice-of-customer analysis or AI workflows. AppTweak’s App Reviews endpoints (Search, Displayed, and Stats) provide exactly this, metered in credits like any other endpoint. For the available filters and response fields, follow the App Reviews reference documentation.
Which API endpoint returns app download and revenue estimates?
AppTweak’s App Metrics endpoints (Current and History) return app download and revenue estimates, and the Category Metrics endpoint returns the same at market level per category and country. Use App Metrics for a single app’s estimated downloads and revenue over time, and Category Metrics for market sizing and benchmarking across a category. Both cover iPhone, iPad, and Android in 100+ countries. The figures are AppTweak’s modeled estimates, useful for competitive benchmarking where first-party numbers are not available. For the exact fields, date ranges, and parameters, follow the App Metrics and Category Metrics reference documentation.
How do AppTweak API credits work?
AppTweak’s App Store API is metered in credits, not per seat or per call, so cost scales with the volume and type of data you request. A broad historical query consumes more credits than a single current lookup, and credit cost varies by endpoint. You authenticate with an API key in the request header, and you can check your remaining balance programmatically with the credits usage endpoint, which makes it straightforward to monitor spend inside your own pipeline. Credit allowances and plan details differ by tier, so check the current pricing page and the pricing reference documentation rather than assuming a fixed allowance.
Is AppTweak’s App Store API suitable for data teams building BI dashboards?
Yes. AppTweak’s App Store API is built for data teams feeding business intelligence (BI) dashboards, because it returns rankings, app download and revenue estimates, category metrics, and keyword data in one consistent schema across the App Store and Google Play. That single schema means the same pipeline handles iOS and Android without special-casing, so teams can pull market data into their warehouse and model it alongside internal metrics such as spend, retention, and revenue. Access is programmatic through REST endpoints and metered in credits. For teams working in AI editors, the remote MCP server exposes the same data for plain-language queries. Start from the API documentation to map each dashboard metric to its endpoint.
More articles in Product Updates
Georgia Shepherd
