Credit management
Every paid API account has a monthly credit allowance. Each API method costs a fixed number of credits per request, and the cost is taken from your balance when the request runs.
How the balance works
- Used credits reset to zero on the 1st of every month.
- When your balance can't cover a request, the API returns HTTP
402("Not enough credits"). Free methods keep working at a zero balance. - Requests that return an error are not charged: the credits held for them go back to your balance.
- Requests rejected before they run (invalid token, missing access to the app or workspace, invalid parameters) are never charged.
Need a higher allowance? Contact AppFollow support.
Method cost
Every method falls into one of these groups:
| Type | Credits | Examples |
|---|---|---|
| Setup and navigation | 0 | List workspaces and users, manage workspaces and users, edit keywords |
| Add or remove an app | 1 | Add app, Remove app |
| Action on one review | 3 | Reply, update tags, notes or bug trackers, report a concern |
| Data read (list or report) | 12 | Reviews feed, rankings, ASO reports, keyword research |
| AI processing | 48 | Reviews AI summary, Reviews semantic tags |
Requests with a date range
Methods that take a date range (from / to) cost 12 credits for the first 14 days, plus 12 credits for every started 14-day block after that. The range length is the number of days between from and to.
Days between from and to | Credits |
|---|---|
| up to 14 | 12 |
| 15–28 | 24 |
| 29–42 | 36 |
| 90 | 84 |
Example: from=2026-01-01&to=2026-01-31 is a 30-day range and costs 36 credits.
The price of every method is listed in Methods cost and availability and on each method's page.
Rate limits
Default limits:
- 3,000 requests per hour per API token
- 10,000 requests per hour per account (all tokens together)
- 100 requests per hour for a sandbox token
When you exceed a limit, the API returns 429 and a Retry-After header with the number of seconds to wait.