How do the JSON output and object table of app store app rank history API of 42 Matters work?

In this article, I will be focusing specifically on the object table and JSON output of the 42 Matters app store app rank history API. I will explain the structure and contents of both the object table and the JSON output, providing examples and further details on how the data is organized and presented. By the end of this article, readers should have a clear understanding of how to interpret and work with the object table and JSON output of this API.

Object and Description table

ObjectsDescription
number_resultsTotal number of results for this query
num_pagesMaximum number of pages it's possible to iterate
has_nextFlag indicating if there is a next page available
limitNumber of results per request
pageCurrent page number
trackIdNumeric unique identifier for the app assigned by Apple
start_dateThe start date of the report
end_dateThe end date of the report
countryCountry code
country_nameName of the country
max_positionThe maximum position in the response
number_datesNumber of dates in the response
datesSorted list of dates in the response
ranksSorted list of rank objects in the response. Each rank contains: primary_genre_id, primary_genre_name, list_name, list_title, date, position
primary_genre_idComma-separated list of App Primary Genre Ids. If no primaryGenreId is specified, all available primaryGenreIds will be returned.
primary_genre_name
list_nameComma-separated list of list_name values. If no list_name is specified, all available list_names will be returned.
list_title
device_typeComma-separated list of Device Types. If no device_type is specified, all available device_types will be returned.
  1. number_results: This object represents the total number of results for a given query.

  2. num_pages: This object specifies the maximum number of pages that can be iterated through for a given query.

  3. has_next: This object is a flag indicating whether there is a next page available in the results for a given query.

  4. limit: This object represents the number of results per request for a given query.

  5. page: This object represents the current page number of the results for a given query.

  6. trackId: This object represents the numeric, unique identifier for an app that is assigned by Apple.

  7. start_date: This object represents the start date of the report for a given query.

  8. end_date: This object represents the end date of the report for a given query.

  9. country: This object represents the country code for the results of a given query.

  10. country_name: This object represents the name of the country for the results of a given query.

  11. max_position: This object represents the maximum position in the response for a given query.

  12. number_dates: This object represents the number of dates included in the response for a given query.

  13. dates: This object represents a sorted list of dates included in the response for a given query.

  14. ranks: This object represents a sorted list of rank objects in the response for a given query. Each rank object contains information such as the primary genre ID, primary genre name, list name, list title, date, and position.

  15. primary_genre_id: This object represents a comma-separated list of app primary genre IDs. If no primary genre ID is specified in the query, all available primary genre IDs will be returned in the response.

  16. primary_genre_name: This object represents the name of the primary genre for an app.

  17. list_name: This object represents a comma-separated list of list name values. If no list name is specified in the query, all available list names will be returned in the response.

  18. list_title: This object represents the title of a list.

  19. device_type: This object represents a comma-separated list of device types. If no device type is specified in the query, all available device types will be returned in the response.

The information in the table is useful because it provides a clear and comprehensive overview of the various objects available in the 42 Matters app store app rank history API. These objects contain a wealth of information about apps, including their unique identifiers, their primary genre, their ranking on various lists, and the dates on which this information was recorded. This information is valuable for anyone looking to track the performance of specific apps or to analyze trends in the app store. Additionally, the inclusion of details such as the country code and the device type allows users to tailor their queries and hone in on specific subsets of data. Overall, the information in the table allows users to fully leverage the capabilities of the API and gain a deep understanding of the data it provides.

Json output

This JSON output represents a query to the 42 Matters app store app rank history API. The output includes several objects that provide information about the query itself, as well as the results of the query. The "number_results" object indicates that there are 80 total results for this query. The "num_pages" object specifies that there are 8 pages of results, and the "has_next" object indicates that there is at least one more page of results available. The "limit" object specifies that there are 10 results per page, and the "page" object indicates that the current page number is 1.

The "trackId" object represents the unique identifier for an app, in this case with a value of "835599320". The "start_date" and "end_date" objects represent the date range for which the results are being returned, in this case from "2022-10-08" to "2022-10-17". The "country" object specifies the country code for the results, with a value of "US", and the "country_name" object provides the corresponding country name of "United States". The "max_position" object indicates that the highest ranking position included in the results is 93.

The "number_dates" object specifies that there are 2 dates included in the results, and the "dates" object is an array containing those dates. The "ranks" object is also an array, containing objects representing the rank of the app for each date. Each rank object includes information about the primary genre of the app, the name and title of the list on which the app is ranked, the device type, the date, and the app's position on the list.

{
"number_results": 80,
"num_pages": 8,
"has_next": true,
"limit": 10,
"page": 1,
"trackId": "835599320",
"start_date": "2022-10-08",
"end_date": "2022-10-17",
"country": "US",
"country_name": "United States",
"max_position": 93,
"number_dates": 2,
"dates": [
"2022-10-08",
"2022-10-09"
],
"ranks": [
{
"primary_genre_id": 6016,
"primary_genre_name": "Entertainment",
"list_name": "topselling_free",
"list_title": "Top Selling Free",
"device_type": "iphone",
"date": "2022-10-08",
"position": 2
},
{
"primary_genre_id": 36,
"primary_genre_name": "Overall",
"list_name": "topgrossing",
"list_title": "Top Grossing Apps",
"device_type": "iphone",
"date": "2022-10-08",
"position": 2
},

Finishing

We have discussed the object table and JSON output of the 42 Matters app store app rank history API. We have explained the structure and contents of both the object table and the JSON output, providing examples and further details on how the data is organized and presented. We have also discussed the usefulness of this information and how it can be used to track the performance of specific apps and analyze trends in the app store. Overall, this information is valuable for anyone looking to work with the data provided by the 42 Matters app store app rank history API.

Endnote

The 42 Matters app store app rank history API is a powerful tool for tracking the performance of specific apps and analyzing trends in the app store. If you are interested in accessing this API, you can do so through the third party data marketplace of Worldindata. Worldindata is a platform that connects users with a variety of data sources, including APIs, and provides a convenient and easy-to-use interface for accessing and working with this data. To request access to the 42 Matters app store app rank history API through Worldindata, simply create an account on the platform and navigate to the API page for the 42 Matters API. From there, you can view more information about the API and submit a request for access. Upon approval, you will be able to start working with the data provided by this API.