How does the InBe API compare to Google Places API?
VS
| Feature | InBe | Google Places API |
|---|---|---|
| Multi-point search | Yes | No |
| Group features | Yes | No |
| Dietary needs | Advanced | Basic |
| Deep preference filtering | Yes | No |
| Rich data in one call | Yes | No |
| Custom location weighting | Yes | No |
| Additional calls for images | No | Yes |
| Menus | Yes | No |
| Events | Yes | No |
| Bookings | Yes | No |
| Results per search | 20 | 20 |
| Good-for contexts (dates, groups, business, etc.) | Advanced | Basic |
| Place highlights (reasons to go) | Yes | No |
Costs comparison
For ease of understanding, the price for each example is based on the assumption that it happens 1000 times.
Let's say you need to find 20 options in-between two users for a date night. They want pizza, but one is gluten-free. Simple, right?
Requirements:
£6
1 Search Request
InBetween
20 tailored and ranked results
£22
2 Geocode Requests
1 Nearby Search Request
Google Places API
~10 results, after you filter reviews for gluten-free
Now lets take the same example, but this time you are creating a dynamic experience for your users, chatting, voting, looking at the menus and images, with the top 5 results.
Requirements:
£66
1 Search Request
5 Advanced Detail Requests (Menus, Images, +)
InBetween
All menu items, events, catering options, and much more
£135
2 Geocode Requests
5 Places Details Requests
5 Places Photos Requests
Google Places API
No menus, events, or details for catering options
Built for a new era of location intelligence
Our goal here is not to bash Google Places API, infact, we think it's great for old, traditional services. We are creating a new era of location intelligence.
One that utlises our connected world, to bridge people looking for great places, with venues that offer unique and exciting offerings.
Our API
Explore our API endpoints, the prices are per 1k requests. Usually, one search request, and 1 to 3 detail requests are used per user(s) session. e.g. two users finding a venue.
Name | Search | Basic | Advanced | Menus |
|---|---|---|---|---|
| Name | ||||
| Display name | ||||
| Formatted address | ||||
| Location coordinates | ||||
| Website | ||||
| Phone | ||||
| Description | ||||
| Primary genre | ||||
| Additional genres | ||||
| Word on the street | ||||
| Opening times | ||||
| Is chain | ||||
| Establishment options | ||||
| Catering options | ||||
| Main image | ||||
| Logo | ||||
| All images | ||||
| Average price per head | ||||
| Special opening times (e.g. Christmas) | ||||
| Kitchen open times | ||||
| Booking link | ||||
| Ratings | ||||
| Accessibility | ||||
| Payment | ||||
| Parking | ||||
| Extra information (e.g. Registered number) | ||||
| Social media links | ||||
| Active menus | ||||
| Active events |
Get Started for Free
Rather then trying to convince you about how great our service is, if you sign up today, we'll give you a tenner in credits (no card required) to use the service and see how it works for your specific use case.
Follow the steps below to get started, or if you have already made your mind up, and want to chat to us about our pricing, or anything else, get in touch.
Get your API Key
Sign up, and once you are redirected to the dashboad, go to the access page and copy your API key.
Get StartedUse our docs and guides to get started
Our comprehensive docs and guides will get you up and running no matter your experience level.
Examples for common use cases mean it takes minutes to start getting perfect venue recommendations.