What's new in release 2017-10-27
We have fresh new data across a number of our data sources. This means our scoring and tagging algorithms use newer data for better recommendations.
New Tours & Activity provider- Musement
We got acquired my Musement recently :). Having their curated list of tours, activities, local events, and tickets in our API is the first step towards creating a single API for content, intelligence, and bookable tours. Watch this space for more!
Query Bookable POIs
We made it even simpler for you to retrieve only POIs that offer ticketing or reservation capabilities. More power to you to help you scale your monetization efforts.
Continous API releases
We figured it would be nicer to have you get access to our product features as we build them as opposed to having them bunched up in quarterly release cycles. We will do away with the number based nomenclature for releases ( i.e v3) and move to naming releases based on their launch date ( for e.g 20171027).
Bug Fixes and more
We also snuck in a few bug fixes and minor enhancements to make the API platform more efficient.
What's new in version v3
We added some powerful features that make intelligent use of our troves of data. These features are aimed at helping our customers improve user engagement and conversions. Here is a snippet on the newbies.
Our new endpoint delivers scores across sightseeing, eating out, nightlife and shopping for any coordinates in the world. It is ideal for accommodation focused OTAs and metasearch players.
Price Rating & Price Information
Our price tiers allow you to classify POIs across 3 price ranges- cheap,medium and expensive, allowing you to display appropriate results for specific customer segments. We also added price information for POIs, when available, to help you determine entrance costs and more.
Now you can filter for tag tabels in a specific district of a city in addition to the tag labels for the city itself. Also we now enable you to query only for “bookable” POIs (i.e POIs that have a booking link) to help you monetize our travel recommendations easily.
One more thing :)
Actually let's make that two. The API now supports negation on our tag labels so that you can exclude specific tag labels you don’t like. Filtering multiple tag labels by score at once also has become super easy with our new child tag labels feature.
Enhanced District coverage
We added districts for many more cities than before. Keep watching this space for exciting addition to the district's & neighborhood data at Triposo.
We took some first steps to make our legendary scoring algorithms a tad easier to understand. Normalization of POI scores upto 10 and tweaks to the algorithms are tweaks with many more in the pipeline.
We exposed GitHub links so you can review the code that powers our demos in our gallery section. Do reach out to us if you like us to feature your demos.
Finally as always we have fresh data from all our data sources.
What's new in version v2
We just moved from a private beta to a public beta! Here is a sneak peek at the features that defined this API release.
The API browser has been prettied up big time for its public beta launch. A cool API balance meter right on the home page gives you a real time view on your API usage and helps you plan your subscription. Additional helpers on the endpoints make it seamless to browse the API even for non-techies. API Content response callouts in the browser now have a visual representation of our data to give you a sense of the quality & comprehensive of the Triposo API platform.
Plans & Billing
The big change to the API console. Thanks to our integration with Stripe we now support subscription billing with three plans targeted at developers, startups and businesses. Select your plan based on your needs, add your credit card on file and seamlessly transition between plans. On-demand credits can also be purchased in a click. All your monthly purchases and invoices are available in the payment history tab with auto-billing in place to ensure you never need to tank up at the end of the month. A trial period helps you test our Pro plan and notifications help you keep tab of usage regularly.
Check out our offering on our neatly designed pricing page. We will continue to add more features differentiated by plans in the future.
We built our own rate limiting and credit management infrastructure to track API requests by plan and ensure users have a superior API browsing experience.
Smarter Querying & Others
We also enabled you to query for POIs that use our similarity engine much easily than before. Also fresher data was included in the mix apart from bug fixes to our image and matching algorithms to improve the quality of our data output. Lastly we also added support for deprecated fields to manage versioning more elegantly in the future.
What's new in version v1
We added a bunch of really cool features in this release. While some are specialized applications that intelligently pull our data and can be used directly on your web or mobile front end, others are enhancement to our existing API product.Here is a snippet on each feature.
They say the best way to experience a city is to “walk” it. We added an endpoint that returns a list of POIs that are ideal for a walk based on a destination and walk time. Our algorithm automatically picks high scoring places of interest across sightseeing, food and other categories.
Planning a trip in a city can be tiresome. We made it as simple as one API call. Add your destination and trip duration and get a complete sightseeing plan split by morning, afternoon and evening sections. Not to forget you also get aptly located recommendations for breakfast, lunch and dinner.
This endpoint is simple and really useful. It returns a list of great food, nightlife and sightseeing options closest to a specific point.
Probably our coolest feature yet. It almost works like magic. You pick a POI that you love in your hometown or favorite city and we return back a list of POIs that are closest to your pick, in a destination city of your choice. This is available as an annotation through the POI endpoint.
Booking Information for POIs
We added a new field called the ‘'booking_info' to the type 'poi'. This provides you the information needed to book a hotel or a restaurant, or purchase entrance tickets to an attraction or a tour that includes access to that POI.
Affiliate ID mgmt for click outs
Related to the booking_info change above, we also added the ability for you to replace the default Triposo IDs with your own affiliate IDs. This allows you to earn 100% of the affiliate commission for the partners integrated with our platform.
We added a new query type called 'exact_negatable' that allows not-equal queries to be expressed. A much smarter way to exclude a particular output from your results.
Endpoint parameters are now annotated in meta.json and the documentation to provide information about default values and whether the parameters are required to be specified or not.
Fields of types are now annotated in meta.json and the documentation to indicate whether or not the corresponding values may be null.
The 'tour' type has new fields ‘duration’ and ‘duration_unit’, providing the tour's duration if known. It also has a new field ‘highlights’ containing a list of tour highlights, as provided by the tour vendor
The 'tags' field of the 'article', 'location', 'poi' and 'tour' types now contains a list of 'tag_with_score' records instead of a list of 'tag' records.
The 'common_tags' endpoint is now deprecated. The new 'common_tag_labels' endpoint should be used instead; it provides the same information as before, but returned in the same format as the other endpoints.
The attribution information for images has been cleaned up. The 'license', 'owner' and 'owner_url' fields of the 'image' type are now deprecated; the contents of the new 'attribution' field should be used instead.
Distances are now returned as integers rather than floats. It looks a bit better on the front end :)
The 'common_parameters' entry in meta.json has been removed; these parameters are now listed explicitly for each endpoint with which they can be used.
The 'related_object' field of the 'image' type has been removed since it is no longer used.
The 'dictionary' and 'related_object' types have been removed since they are no longer used.