Outdoor seating as a structured field, not a guess.

InBetween records patios, terraces, heated gardens, and covered spaces as first-class attributes, so your product can answer 'somewhere we can sit outside' with confidence.

Get Started
api.inbe.us/v1/search200 OK
POST
{
"locations": [
{ "lat": 51.5072, "lon": -0.1276, "weight": 30 },
{ "lat": 51.5154, "lon": -0.1419, "weight": 40 },
{ "lat": 51.5034, "lon": -0.1195, "weight": 30 }
],
"mode": {
"mode": "POINT"
"maxDistance": 200
},
"preferences": {
"openingConditions": {
"state": "ANY"
"atTime": "2026-08-15T17:53:51.178Z"
},
"goodFor": ["family", "coffee", "date"]
"catersFilters": ["vegetarian", "glutenFree", "vegan"]
"establishmentFilters": ["restaurant"]
}
}

For products where the weather shapes the plan

One of the most asked questions, and the hardest to answer.

'Can we sit outside?' decides more plans than almost any other question, and it changes with the season: sunny terraces in summer, covered patios in spring, heated gardens when it turns cold.

Most place data buries the answer in review text, if it holds it at all. Teams end up parsing prose, and users end up phoning the venue or gambling on arrival.

InBetween records outdoor spaces as structured attributes: what kind of space it is, whether it is covered or heated, and how to find it. Your product can filter on it as reliably as it filters on cuisine.

What breaks today

  • Outdoor details live in review prose, not in queryable fields.
  • Category tags cannot distinguish a heated garden from two pavement tables.
  • Users leave to verify outdoor space elsewhere, and often do not come back.

What you can ship

  • An outdoor filter that returns venues that genuinely have the space.
  • Seasonal features that combine weather, diet, vibe, and distance.
  • Fewer users leaving your product to double-check the details.

How it works for you

  1. 01

    Offer an outdoor filter users can trust

    Filter by patio, terrace, garden, or covered space directly, rather than hoping a category tag implies one.

  2. 02

    Combine it with the rest of the plan

    Outdoor seating works alongside dietary needs, atmosphere, budget, and distance in a single request.

  3. 03

    Guide people to the right entrance

    Access notes and entrance details help users find the terrace, not just the address.

Built into the broader InBetween platform

This capability sits alongside the rest of our hospitality venue intelligence—so you can combine filters, search, and decision tools in one product surface.

Every venue. Every detail.

Precision metadata for apps that help people meet, eat and drink.

Venue intelligence

Ultra detailed venue data

Get detailed information about venues, including menus, pricing, ambiance, and more.
Smart matching

Preference driven

Wow your customers with recommendations and information tailored for them.
Multi-location search

Tools for multiple locations. Find restaurants, bars and cafés based on multiple sets of preferences and locations.

In-app experience

Loyal to you

Keep users inside your app by giving them the info they need to make decisions.
Decision support

Built for decision-making

A suite of tools designed to enable you to answer customer needs directly.

Every venue. Every detail.

Precision metadata for apps that help people meet, eat and drink.

Venue intelligence

Ultra detailed venue data

Get detailed information about venues, including menus, pricing, ambiance, and more.
Smart matching

Preference driven

Wow your customers with recommendations and information tailored for them.
Multi-location search

Tools for multiple locations. Find restaurants, bars and cafés based on multiple sets of preferences and locations.

In-app experience

Loyal to you

Keep users inside your app by giving them the info they need to make decisions.
Decision support

Built for decision-making

A suite of tools designed to enable you to answer customer needs directly.

Outdoor seating, structured

Answer 'can we sit outside?' with confidence.

Open up a new world for your users with InBe's preference-aware venue discovery—built for group venue matching, dietary search, and ranked shortlists.

No card required. Full core API access.

Keep exploring

Questions teams ask

Built for developers who connect people to places

Connecting users to real-world places shouldn’t mean stitching geocoding, routing, Places search, and ranking yourself. One preference-aware search replaces the pipeline.

api.inbe.us/v1/search200 OK
POST
{
"locations": [
{ "lat": 51.523, "lon": -0.158, "label": "Alex" },
{ "lat": 51.493, "lon": -0.098, "label": "Sam" }
],
"mode": { "mode": "POINT", "maxDistance": 750 },
"preferences": {
"goodFor": ["date", "cocktails", "conversation"],
"catersFilters": ["vegetarian"],
"establishmentFilters": ["servesCocktails"]
}
}
response
{
"centerPoint": { "Lat": 51.508, "Lon": -0.128 },
"radius": 750,
"establishments": [
{
"displayName": "The Lantern Room",
"distanceMeters": 142,
"matchScore": { "total": 0.94 }
},
{
"displayName": "Barrio Soho",
"distanceMeters": 186,
"matchScore": { "total": 0.91 }
}
]
}

Fair middlegrounds

Multi-person locations in one call; we balance travel so you don’t build routing yourself.

Preferences that actually match

Dietary, vibe, good-for, and constraints as first-class inputs, not post-filters on pins.

Pay for the hard parts

Core search and enriched place data stay cheap; you pay where decision intelligence earns its keep.

Tools for user decisions

Ranked shortlists and experience-ready answers so your product keeps users in-flow, not off to a map.

Illustrative scenario

0ms

Ranked shortlist in one call

Preference-aware search returns a decision-ready shortlist without stacking Places, routing, and enrichment calls.

~15× faster vs multi-call pipelinesNot a live benchmark
RESTWorks with any stack
curl -X POST https://api.inbe.us/v1/search \
  -H "API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "locations": [
      { "lat": 51.523, "lon": -0.158, "label": "Alex" },
      { "lat": 51.493, "lon": -0.098, "label": "Sam" }
    ],
    "mode": { "mode": "POINT", "maxDistance": 750 },
    "preferences": {
      "goodFor": ["date", "cocktails", "conversation"],
      "catersFilters": ["vegetarian"],
      "establishmentFilters": ["servesCocktails"]
    }
  }'

Start in minutes with the knolage you can scale without stress.

Generous free usage to evaluate, startup credits to grow, and a migration path when you are ready to switch from stacked Places pipelines.