Semantic Analysis for Hostel Reviews API

API ID 877

The Semantic Analysis for Hostel Reviews API allows users to analyze customer reviews of hostels and retrieve information about the key themes and sentiments expressed in the reviews. The API returns a list of keywords and phrases, as well as a sentiment score for each review.

100% uptime 1,898 ms avg response

API Documentation

Endpoints

Request

This endpoint returns all results in one output: general sentiment, aspects, categories, semantic analysis, and a semantic summary. 

Endpoint ID: 664
POST https://zylalabs.com/api/877/semantic+analysis+for+hostel+reviews+api/664/analysis
INPUT PARAMETERS

Analysis — Endpoint Features

Object Description
text Required The review to analyze.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

text
API EXAMPLE RESPONSE
JSON
{"general_sentiment":0.714,"categories":{"0":{"name":"location","count":1,"sentiment_score":1},"1":{"name":"hostel","count":3,"sentiment_score":1.667},"2":{"name":"service","count":1,"sentiment_score":-1},"3":{"name":"price","count":2,"sentiment_score":0}},"aspects":{"0":{"name":"close to","count":1,"sentiment_score":1},"1":{"name":"opinion","count":2,"sentiment_score":2},"2":{"name":"check-in","count":1,"sentiment_score":-1},"3":{"name":"common room","count":1,"sentiment_score":1},"4":{"name":"payment","count":2,"sentiment_score":0}},"semantic_analysis":{"0":{"id_semantic_model":179,"name_semantic_model":"close_to_airport","description":"The hostel is close to the airport, short drive, minutes from airport","id_opposite_semantic_model":null,"category":"location","aspect":"close to","feature":"airport","polarity":1,"segment":"We only stayed at this hostel for one night because it was convenient to the airport"},"1":{"id_semantic_model":226,"name_semantic_model":"overall_good_satisfied","description":"The customer was satisfied in general, good overall, nice stay, good experience, good place, enjoyable experience, everything we needed, met my expectations","id_opposite_semantic_model":228,"category":"hostel","aspect":"opinion","feature":"overall good, satisfied","polarity":2,"segment":"We only stayed at this hostel for one night because it was convenient to the airport"},"2":{"id_semantic_model":231,"name_semantic_model":"check_in_slow_bad","description":"Check-in/out was slow, took forever, early check in not permitted, long lines, queue, took over an hour, inconvenient","id_opposite_semantic_model":227,"category":"service","aspect":"check-in","feature":"slow","polarity":-1,"segment":"The check in process took 30 minutes, which frustrated us because there were a lot of people checking in at the same time"},"3":{"id_semantic_model":325,"name_semantic_model":"common_social_room_available","description":"The common area was available, there is common area, big social area","id_opposite_semantic_model":349,"category":"hostel","aspect":"common room","feature":"available","polarity":1,"segment":"The shared bathrooms weren't too crowded and the common room had billiards and ping pong"},"4":{"id_semantic_model":120,"name_semantic_model":"bill_problems","description":"There was a problem with the bill/payment, payment problems, double charged, incorrectly charged, card mix up, bill mess up, problem with paper receipt","id_opposite_semantic_model":null,"category":"price","aspect":"payment","feature":"bill problem","polarity":-1,"segment":"However, we did have some issues with the payment because they only accepted cash"},"5":{"id_semantic_model":72,"name_semantic_model":"hostel_adequate_price","description":"The hostel was reasonably priced, good price, hostel adequate priced, good deal, worth the money, good value, good experience for the price","id_opposite_semantic_model":71,"category":"price","aspect":"payment","feature":"adequate price","polarity":1,"segment":"Despite this, the hostel offered good value for the money"},"6":{"id_semantic_model":226,"name_semantic_model":"overall_good_satisfied","description":"The customer was satisfied in general, good overall, nice stay, good experience, good place, enjoyable experience, everything we needed, met my expectations","id_opposite_semantic_model":228,"category":"hostel","aspect":"opinion","feature":"overall good, satisfied","polarity":2,"segment":"Overall, it was a good choice for a one night stay"}},"semantic_summary":{"0":"The hostel is close to the airport","1":"The customer was satisfied in general","2":"Check-in/out was slow","3":"The common area was available","4":"There was a problem with the bill/payment","5":"The hostel was reasonably priced"}}
Analysis — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/877/semantic+analysis+for+hostel+reviews+api/664/analysis?text=We only stayed at this hostel for one night because it was convenient to the airport. The check-in process took 30 minutes, which frustrated us because there were a lot of people checking in at the same time. Besides that, our experience at the hostel was positive. The shared bathrooms were not too crowded and the common room had billiards and ping-pong. However, we did have some issues with the payment because they only accepted cash. Despite this, the hostel offered good value for the money. Overall, it was a good choice for a one-night stay.' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Semantic Analysis for Hostel Reviews API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

About the API:

The Semantic Analysis for Hostel Reviews API allows users to analyze customer reviews of hostels and retrieve information about the key themes and sentiments expressed in the reviews. The API returns a list of keywords and phrases, as well as a sentiment score for each review, with a score of 1 indicating a positive review and a score of -1 indicating a negative review. This API is useful for hostel owners looking to understand the key themes and sentiments expressed in customer reviews and for travelers looking to get a sense of the overall sentiment of reviews for a particular hostel.

 

What this API receives and what your API provides (input/output)?

Pass the text that you want to analyze and receive the different intentions within it with the sentiment score. 

 

What are the most common uses cases of this API?

  1. A hostel booking website or app could use the API to provide users with a summary of the key themes and sentiments expressed in reviews for a particular hostel.

  2. A hostel management platform could use the API to help hostel owners understand the key issues and areas of satisfaction mentioned in customer reviews, in order to improve their business.

  3. A travel website or app could use the API to help tourists get a sense of the overall quality and reputation of a hostel before booking a stay.

  4. A hostel review website or app could use the API to automatically categorize and summarize customer reviews for display on the website or app.

  5. A market research firm could use the API to gather and analyze customer reviews for a range of hostels in order to track trends and identify key drivers of customer satisfaction.

  6. A customer service platform could use the API to automatically classify and route customer reviews to the appropriate department or team for follow-up.

 

Are there any limitations to your plans?

Besides the number of API calls per month, there is a limitation of 1 request per second. 

Semantic Analysis for Hostel Reviews API FAQs

The Analysis endpoint returns a comprehensive output that includes general sentiment, categories, aspects, semantic analysis, and a semantic summary of the provided review text.

Key fields in the response include "general_sentiment," "categories" (with names and sentiment scores), "aspects" (with names and sentiment scores), and "semantic_analysis" (detailing specific sentiments and descriptions).

The response data is structured as a JSON object, with nested objects for categories, aspects, and semantic analysis, allowing users to easily access detailed sentiment and thematic information.

The Analysis endpoint provides insights into customer sentiments, key themes, and specific aspects of hostel reviews, such as location, service, and price, helping users understand overall customer satisfaction.

Users can customize their requests by providing different review texts for analysis, allowing the API to return tailored insights based on the specific content of each review.

"general_sentiment" indicates overall sentiment (positive or negative), "categories" represent themes like "location" or "service," and "aspects" provide detailed sentiments related to specific features mentioned in the reviews.

Data accuracy is maintained through advanced semantic analysis algorithms that evaluate the context and sentiment of reviews, ensuring reliable insights into customer opinions and experiences.

Typical use cases include summarizing reviews for booking platforms, helping hostel owners identify improvement areas, and enabling travelers to gauge hostel quality before making reservations.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs