API plans

You can find more info about our the pricing of our API subscription and the number of credits per plan in the API Subscription Pricing section.

Pricing principles

AppTweak has designed the API pricing around 3 core principles:

All data are not created equal: some data points are easier to fetch, store, and compute than others. As a consequence, the pricing will change depending on the kind of data requested.
App stores evolve on a day-to-day basis— but not significantly. As a consequence, requesting the evolution of the same value(s) over a specific date range should not cost a multiple of the first data point.
AppTweak won't always be able to return values in the past. As a consequence, we take great care to not charge for "unknown" data points.

The algorithm used to charge your account works as follows:

When receiving a request, we compute the maximum cost incurred by the request based on the requested data. This cost is based on the parameters of the request, assuming that every single requested data point is available in our database.
If your account has enough credits, we gather the requested data from our databases.
We compute the actual cost of the request by inspecting the response we are giving back and removing the cost for any missing data.
Your account will only be charged for that final cost.

Price per request

As you can see on the left-side menu, our API endpoints are split between current and historical.

Current endpoints:
Current endpoints allow you to query data points and get the last known value available in our database. The price of these requests is determined as:

price = 1
FOR EACH app requested (if applicable)
  FOR EACH keyword requested (if applicable)
    FOR EACH requested data point
    	IF data point available
      	price = price + base data point price
      END
    END
  END
END

This means that you effectively pay the data point price for each requested element, but only if it's available.

Historical endpoints:
Historical endpoints allow you to query data points over a date range and get the daily values over that date range. The price of these requests is determined as:

price = 1
FOR EACH app requested (if applicable)
  FOR EACH keyword requested (if applicable)
    FOR EACH requested data point
      FOR EACH date IN requested date range
        IF data point available on date
          IF first available data point on date range
          	price = price + base data point price
          ELSE
            price = price + base data point price / 10
          END
        END
      END
    END
  END
END

This means that you pay the full price for each element for the first available data point in the date range, but each additional day only costs 10% of the base price.

Price per data point

Category	Datapoint name	Endpoints served	credit base price	credit/extra day
App Metadata	applies to all attributes	App Metadata - Current	10
App Metrics	downloads	App Metrics - Current/History	500	50
	revenues	App Metrics - Current/History	500	50
	app_power	App Metrics - Current/History	10	1
	ratings	App Metrics - Current/History	10	1
App Category Ranking		App Category Ranking - Current/History	10	1
App Keyword Ranking	rank	App Keyword Ranking - Current/History	10	1
	installs	Apps - Keywords Metrics Current/History	10	1
App Reviews	review	App Reviews Displayed	1
	review	App Reviews Search	1
	review	App Reviews Stats	10	1
Keyword Metrics	volume	Keyword Metrics - Current/History	10	1
	difficulty	Keyword Metrics - Current	10
	is_branded	Keyword Metrics - Current	10
	results	Keyword Metrics - Current/History	10	1
	max_reach	Keyword Metrics - Current	10
Keyword Search		Keyword Search - Current/History	50	5
Keyword Suggestions	keyword	Keyword Suggestions - App	1
	keyword	Keyword Suggestions - Category	10
	keyword	Keyword Suggestions - Trending	10
	keyword	Keyword Suggestions - Volume Change	10
Top Charts		Top Charts Current/History	10	1
DNA Charts		DNA Charts Current	50
Conversion Rate Benchmarks	category_benchmarks	Conversion Rate Benchmarks - History	1000
Category Metrics	downloads	Category Metrics - History	1000	100
	revenues	Category Metrics - History	1000	100
Twin App	twin app	Twin App	50
CPP Intelligence	cpp	CPP by App	500	50
	cpp	CPP by Category	500	50
	cpp	CPP by DNA	500	50
	cpp	CPP by keywords	500	50
	cpp	CPP Keywords	500	50

Example

Example: a request returns download estimates for 45 days for 1 app. The number of necessary credits is 1 (cost of request) + 500 (datapoint base price) + 44 (days) * 50 credits (per extra day) = 2701 credits