The most common mistake when calling app-related endpoints is using the wrong DateTime format. Endpoints that use a DateTime input, require an ISO DateTime format without the milliseconds part which looks like this: yyyy-MM-ddTHH:mm:ss. Here:

• yyyy: year, e.g., 2015
• MM: month, e.g., 03
• dd: day, e.g., 27
• T: separator
• HH: hour, e.g., 08
• mm: minute, e.g., 45
• ss: second, e.g., 13

For example, to search for reviews from 2016-07-14 noon, the dateFrom parameter would look like this: “2016-07-14T12:00:00”.

Remember that neither dateFrom nor dateTo dates cannot be set to the date in the future and dateFrom should be less than dateTo.

Example of correctly calling the App Topics API endpoint (Python)

In this example, we will be requesting topics of an application between the period of 2020-01-01 00:00:00 (dateFrom) and 2020-12-01 00:00:00 (dateTo).

import requests

url = "https://netgeist-app-review-monitoring.p.rapidapi.com/app/<APP_ID>/topics"

querystring = {"dateFrom":"2020-01-01T00:00:00","dateTo":"2020-12-01T00:00:00"}

headers = {
	"X-RapidAPI-Key": "<YOUR_API_KEY>",
	"X-RapidAPI-Host": "netgeist-app-review-monitoring.p.rapidapi.com"
}

response = requests.request("GET", url, headers=headers, params=querystring)

print(response.text)

In the code above, replace <APP_ID> with the ID of the app you want to get the topics for, and <YOUR_API_KEY> with your RapidAPI API key.

If called correctly, the request should return similar results:

{
  "app_topics": [
    {
      "game": {
        "review_count": 15,
        "positive_count": 6,
        "neutral_count": 4,
        "negative_count": 5
      }
    },
    {
      "chess": {
        "review_count": 8,
        "positive_count": 5,
        "neutral_count": 2,
        "negative_count": 1
      }
    }
  ]
}

Code examples in most programming languages are provided in the NetGeist API Endpoints page.

For more information, visit netgeist.ai or contact us at info@netgeist.ai.