Starting Tuesday, November 3, 2026, the AppTweak API moves to a new credit system. The goal is simple: you should know what a call costs before you make it, and get more data for the same plan price.
This article explains the changes in detail. If you use the API through scripts, dashboards or integrations, the section "What to check in your scripts" is the most important part.
Quick summary
Your plan price doesn't change.
1 new credit = 10 old credits. Your monthly credit count looks smaller, but calls cost proportionally less. Most workflows use far fewer credits than before.
One rule for most calls. Most API calls now cost a standard 1 credit for current data and 5 for historical data.
Query parameters and response formats don't change. Your existing requests keep working and return data in exactly the same structure.
One new limit: historical requests can cover up to 1 year per call. This may require small updates to your scripts.
Existing customers get 10% more credits, for as long as they stay subscribed, and keep every feature of their current plan.
Why we're changing our credit system
Today, the cost of a call depends on many variables: number of apps, metrics, keywords and extra days of history. That makes usage hard to predict, and a single large request can use up a big share of a monthly allowance.
The new system follows one rule: you pay for the data you get, at a price you can calculate in advance.
What stays the same
We designed this change so that your integrations keep working as they are:
Same endpoints. No endpoint is renamed or removed.
Same query parameters. The parameters you send today are accepted and behave the same way.
Same response format. Responses keep the same structure, fields and data types.
Same API keys and MCP connections. Nothing to regenerate or reconnect.
Same plan prices and features. Lite, Pro, Power, and Enterprise keep their names and prices, and you keep everything your current plan includes, including download and revenue estimates if you use them today.
What to check in your scripts
1. Historical data: maximum 1 year per call
Up to today, there was no limit to the date range you can request in a single call. From November 3, each call can cover up to 1 year of history. Requests covering more than 1 year will return an error.
What to do: if any of your scripts request more than 1 year in a single call, split them into several calls of up to 1 year each. For example, to get 3 years of history, make 3 calls of 1 year each.
You still have access to up to 10 years of historical data. Only the range of a single call is limited.
2. Maximum keywords and categories per call
From November 3, each call returns data for up to:
10 keywords for keyword metrics
5 keywords for rankings
5 categories
If a request includes more, only the first ones up to the limit are returned.
What to do: if your scripts send more keywords or categories in a single call, split them into batches that fit these limits. You don't pay more for using the full batch: keywords and categories don't multiply the cost of a call.
3. Credit values returned by the API
Because 1 new credit equals 10 old credits, every credit figure is divided by 10. This applies to:
the credit cost returned with each API response
the balance returned by the credits balance endpoint
your monthly allowance and remaining balance in your account
The fields and their format stay the same; only the values change.
What to do: if you have scripts or alerts that track credit usage (for example, "alert me when fewer than 50,000 credits remain"), divide those thresholds by 10.
4. Requests that return no data
A request that returns no data because of the request itself (for example, asking for an app in a country where it isn't available) costs 1 credit. Errors on AppTweak's side are free.
What to do: if your scripts loop over many countries or apps to check availability, keep in mind that each empty result uses 1 credit.
How credits work
The core rule
A call now costs 1 standard credit per app and per metric for current data, and 5 credits per app and per metric for historical data, whatever the period requested (up to 1 year).
Data | Current | History |
Apps, keywords, charts, reviews | 1 per app per metric | 5 per app per metric |
Download & revenue estimates | 10 per app per metric | 50 per app per metric |
Integrations (App Store Connect, Google Play Console) | 1 per call | 1 per call |
Example: asking for rating and app power (2 metrics) for 3 apps costs 2 × 3 = 6 credits for current data, or 30 credits for history.
What doesn't multiply
Keywords, categories, and number of reviews don't multiply the cost. They're included in the price of the call, within the limits defined by the endpoints.
What it costs in practice
Use case | Credits before Nov 3 | Credits from Nov 3 |
App metadata lookup (1 app) | 11 | 1 |
Keyword audit: 1 app, 100 keywords, with rank trend | 16,950 | 360 |
Keyword research: 50 ideas + top 3 results | 1,209 | 41 |
Review analysis: 500 reviews + rating trend | 541 | 6 |
ASO dashboard: 10 apps × 100 keywords, refreshed daily for a month | 318,360 | 6,980 |
Since new credits are worth 10 old ones, a use case gets cheaper when its new cost is less than a tenth of today's. That's the case for each example above.
Your plan after the change
Whether you’ve used our API for years or just a few weeks, we want to say thank you for building with us.
Among these changes, we’ve added 10% extra credits to every existing API plan, which stays for as long as you do (including when you renew).
On November 3rd:
Your monthly counter resets to full, so you start the new system with your complete allowance.
Remaining one-time credits are converted: divided by 10, then increased by 10%. For example, 2,574 remaining credits become 284.
Integration data (App Store Connect, Google Play Console) is included in every plan.
FAQ
Will I pay more?
No. Your plan price stays the same. Your credit count looks smaller because each credit is worth 10 old credits, but calls cost proportionally less.
Do I need to change my code?
Only if you request more than 1 year of history in a single call, send more keywords or categories per call than the limits above, or track credit values against fixed thresholds. Endpoints, query parameters and response formats don't change.
Why does my plan show 22,000 credits instead of 200,000?
200,000 old credits equal 20,000 new credits. Your 10% loyalty bonus brings it to 22,000.
I use download and revenue estimates. Do I keep them?
Yes. Existing customers keep access to estimates on their current plan.
Does the 10% bonus expire?
No. It applies for as long as you stay subscribed.
Who can I contact?
Reply to the announcement email or contact [support@apptweak.com]. We're happy to help you check your scripts or estimate your usage under the new system.