Recensia
Recensia
verified icon
500 atoms
AI tier

About

This API allows you to retrieve app reviews from the Apple App Store and Google Play Store.
This API is designed to provide developers and product teams with easy access to user feedback, enabling them to analyze trends, improve app performance, and address user concerns efficiently.

API Playground

API Documentation

Get Reviews
POST
https://api.apyhub.com/recensia/analyse_reviews

Request example

1
```cURL
2
3
curl --location --request POST 'https://api.apyhub.com/recensia/analyse_reviews' \
4
--header 'apy-token: {{token}}' \
5
--header 'Content-Type: application/json' \
6
--data '{
7
"platform" : "app_store",
8
"country" : "us",
9
"app_id" : "368677368",
10
"sort_by": "mostrecent"
11
}'
Method: POST
Content Type: application/json
Request Body
AttributeMDescriptionAccepted Values / Format
platformYesThe platform from which to retrieve reviews.app_store, google_play
app_idYesThe unique identifier of the app on the specified platform.String
countryRequired if platform is app_storeThe country code (ISO 3166-1 alpha-2) for filtering reviews from a specific region.Example: US (for the United States)
languageRequired if platform is google_playThe language code (ISO 639-1) for filtering reviews by language.Example: en (for English)
start_dateNoThe start date to filter reviews.Format: YYYY-MM-DD
end_dateNoThe end date to filter reviews.Format: YYYY-MM-DD
sort_byYesThe parameter by which to sort the reviews.For app_store: mostrecent, mosthelpful, mostfavorable, mostcritical
For google_play: mostrelevant, newest, rating
Sample Response
A successful request returns the extracted data from document as response in the output parameter specified. If the request fails, the response contains an error code and a message to help determine what went wrong.
1
{
2
"message": {
3
"review_count": 200,
4
"word_count": 5322,
5
"reviews_min_date": "2024-11-18",
6
"reviews_max_date": "2024-11-20",
7
"rating": 4.9,
8
"downloads": null,
9
"preamble": "We have analyzed 200 reviews, which consist of 5 322 words, written by users from US.\nHere is what we learned.",
10
"content": "### Summary Report on App Store Reviews for the App\n\n#### 1. **Positive Experiences**\n - **Driver Quality**: Many users praised the drivers for being friendly, professional, and courteous. Specific mentions of drivers who provided excellent service, engaged in pleasant conversations, and ensured a comfortable ride were common.\n - **Convenience and Ease of Use**: Users appreciated the app's convenience, highlighting the ease of booking rides and the quick response times in getting drivers. Many noted that the app made their travel experiences stress-free.\n - **Cleanliness and Comfort**: Several reviews mentioned the cleanliness of the vehicles, with users expressing satisfaction with the comfort of their rides.\n - **Timeliness**: Many users reported that drivers arrived on time or even early, which contributed to a positive overall experience.\n\n#### 2. **Negative Experiences**\n - **Driver Issues**: Some users reported problems with drivers, including instances where drivers did not arrive, were unresponsive, or provided poor navigation. A few reviews mentioned being paired with the same driver after canceling due to dissatisfaction.\n - **Pricing Concerns**: A significant number of reviews expressed frustration over pricing, with users feeling that fares were often higher than expected. Complaints about sudden fare increases, additional charges, and perceived overpricing were prevalent.\n - **App Functionality**: Several users reported issues with the app itself, including crashes, difficulties in tracking rides, and problems with payment processing. Some users mentioned that the app was confusing and lacked adequate customer support.\n - **Customer Support**: Many users expressed dissatisfaction with the customer support experience, citing difficulties in reaching support and receiving timely assistance for issues encountered.\n\n#### 3. **Mixed Reviews**\n - **Ride Quality**: While many users had positive experiences with their rides, some reported inconsistent experiences, with a few rides being less satisfactory than others. This inconsistency led to mixed feelings about the overall service.\n - **Promotions and Offers**: Some users appreciated promotional offers but also expressed confusion or dissatisfaction regarding the terms and conditions associated with these promotions.\n\n#### 4. **Suggestions for Improvement**\n - **Enhanced Customer Support**: Users suggested that the app should improve its customer support system, making it easier to contact representatives and resolve issues.\n - **Transparent Pricing**: Many users called for clearer communication regarding pricing, including upfront costs and potential additional fees.\n - **App Stability**: Users recommended improvements to the app's stability and functionality to prevent crashes and enhance user experience.\n\n### Conclusion\nOverall, the app has garnered a mix of positive and negative feedback. While many users appreciate the convenience, quality of drivers, and overall ride experience, there are significant concerns regarding pricing transparency, app functionality, and customer support. Addressing these issues could enhance user satisfaction and loyalty."
11
}
12
}

HTTP Response Codes

The method may return one of the following HTTP status codes:
HTTP Status CodeDescriptionExample
200 OKRequest was successful.N/A
400 Bad RequestReturned if one or more required parameters are missing or invalid.{"country": "This field is required for app_store platform."}
{"language": "This field is required for google_play platform."}
500 Internal Server ErrorReturned if an internal issue occurs while processing the request.N/A

Authentication

All API requests to ApyHub services need to be authenticated. Currently we support tokens or basic authentication mechanisms. You can generate and view your existing credentials from your workspace settings (on the left side of the navbar) and go to “API Keys".
Points to note:
  • Credential secrets are generated on the fly and are not stored in plain text, so on generating a credential please save the secrets somewhere safe.
  • Use the apy-token as the header parameter to pass the token.
  • Use the Authorization header to send the basic authentication credentials.

Error codes

1
{
2
"error": {
3
"code": 105,
4
"message": "Invalid URL"
5
}
6
}
To search for a specific error code, enter the code in the search box below. Alternatively, you can click on the button to view a complete list of all error codes.
Table of contents
AboutAPI PlaygroundAPI DocumentationAuthenticationError codesRelated Utility APIsRelated Articles