SearchGET/search_bycoordinates

Vrbo /search_bycoordinates API

Power your real estate application with reliable /search_bycoordinates data from Vrbo. This endpoint is built on infrastructure that processes millions of requests daily with consistent sub-second latency and high availability across all regions. Unlike DIY scraping solutions that degrade over time and require constant maintenance, RealtyAPI provides a stable interface that your team can depend on quarter after quarter. The data is fresh — every request fetches live information from Vrbo — and the response format is designed for easy parsing and storage. It is the kind of data infrastructure that lets your engineering team focus on product work instead of plumbing.

What You Can Do With the /search_bycoordinates Endpoint

Here's what this endpoint provides and how you can use the data it returns.

Endpoint Parameters

Parameter	Type	Required	Description
`latitude`	NUMBER	Required	Decimal latitude (-90 to 90). Internally reverse-geocoded to the nearest Vrbo region.
`longitude`	NUMBER	Required	Decimal longitude (-180 to 180).
`radius`	NUMBER	Optional	Search radius in miles. Default `10`. Only used for distance-based ranking — Vrbo natively filters by region not by point-radius.
`checkIn`	STRING	Optional	ISO check-in date `YYYY-MM-DD`. Must be paired with `checkOut`.
`checkOut`	STRING	Optional	ISO check-out date `YYYY-MM-DD`. Must be paired with `checkIn`.
`adults`	NUMBER	Optional	Adult guests (ages 13+). Default `2`.
`children`	STRING	Optional	Comma-separated child ages, e.g. `4,8`. Ages 0-17.
`priceRange`	STRING	Optional	Nightly or total price (basis controlled by `pricingType`). Possible Inputs: - For Minimum: `min:100` - For Maximum: `max:600` - For a Range: `min:100,max:600` Values are USD integers.
`pricingType`	ENUM	Optional	Price-range basis. `nightly` (default) compares to the listing's per-night rate; `total` compares to the all-in total for the selected dates. Values: `nightly, total`
`bedrooms`	STRING	Optional	Minimum bedrooms. Format `min:N` (Vrbo only filters on a floor, not a range). Example: `min:2`.
`bathrooms`	STRING	Optional	Minimum bathrooms. Format `min:N`. Example: `min:1`.
`propertyType`	STRING	Optional	Comma-separated property types. Multi-select supported. Common values: `house`, `villa`, `cabin`, `apartment`, `condo`, `townhouse`, `cottage`, `bungalow`, `studio`, `boat`, `chalet`, `treehouse`, `resort`, `bed_and_breakfast`, `farmhouse`, `hotel`, `estate`, `guesthouse`, `lodge`, `yacht`.
`amenities`	STRING	Optional	Comma-separated amenities. Common values: `private_pool`, `hot_tub`, `pool`, `wifi`, `kitchen`, `air_conditioning`, `parking`, `washer`, `dryer`, `fireplace`, `gym`, `pet_friendly`, `balcony`, `bbq`, `sauna`, `electric_vehicle_charger`, `boat_rentals`, `bike_rentals`.
`commonSpaces`	STRING	Optional	Comma-separated indoor / outdoor common spaces. Values: `kitchen`, `dining_room`, `living_room`, `outdoor_space`, `office`, `game_room`.
`rating`	STRING	Optional	Guest-rating floor. Single value. Values: `wonderful_9` (Wonderful 9+), `very_good_8` (Very Good 8+), `good_7` (Good 7+).
`houseRules`	STRING	Optional	Comma-separated house-rule filters. Values: `pets_allowed`, `no_pets_allowed`, `events_allowed`, `non_smoking`.
`nearbyActivities`	STRING	Optional	Comma-separated nearby-activity filters. Values: `theme_parks`, `fishing`, `golfing`, `skiing`, `cycling`, `hiking`, `snorkeling`, `surfing`, `boating`, `horseback_riding`.
`accessibility`	STRING	Optional	Comma-separated accessibility filters. Values: `wheelchair_accessible`, `single_level_property`, `accessible_pool`, `step_free_entrance`, `elevator`.
`areaType`	STRING	Optional	Comma-separated area-type filters (UI: "Location" section). Values: `lake`, `downtown`, `golf_course`, `beach`, `mountain`, `city_center`, `ski`, `rural`, `village`, `waterfront`.
`beach`	STRING	Optional	Beach proximity. Comma-separated. Values: `on_the_beach`, `near_the_beach`.
`goodFor`	STRING	Optional	Properties highly rated for. Comma-separated. Values: `cleanliness`, `families`, `location`, `value`.
`discounts`	STRING	Optional	Discount filters. Comma-separated. Values: `weekly_discount`, `monthly_discount`, `new_listing_discount`, `last_minute_booking`.
`premierHost`	BOOLEAN	Optional	Set to `true` to return only Premier Host listings (Vrbo's vetted-host badge).
`freeCancellation`	BOOLEAN	Optional	Set to `true` to return only listings offering free cancellation.
`instantConfirmation`	BOOLEAN	Optional	Set to `true` to return only listings with instant confirmation.
`onlyAvailable`	BOOLEAN	Optional	Set to `true` to hide listings not available on the requested `checkIn` / `checkOut` dates.
`neighborhoodId`	STRING	Optional	Numeric Vrbo neighborhood IDs (comma-separated). Discover via `/autocomplete` — each suggestion includes its `regionId`.
`sortOrder`	ENUM	Optional	Result sort order. Default `Recommended`. Values: `Recommended, Price_Low_to_High, Price_High_to_Low, Distance, Review_Rating, Most_Reviewed`
`page`	NUMBER	Optional	1-based page number. Default `1`.
`resultCount`	NUMBER	Optional	Listings per page (1-200). Default `50`.

Required Parameters

This endpoint requires latitude, longitude to fetch data. Pass these as query parameters in your request.

JSON Response

Receive structured JSON containing /search_bycoordinates data from Vrbo. Parse it directly into your application models.

Real-Time Results

Every request fetches live Vrbo data. No stale caches — you always get the most current information available.

Error Handling

Clear HTTP status codes and error messages help you handle edge cases gracefully. See our documentation for the full error reference.

Quick Start Example

Make your first request to the /search_bycoordinates endpoint in seconds.

Python

import requests

url = "https://vrbo.realtyapi.io/search_bycoordinates"

headers = {
    "x-realtyapi-key": "YOUR_API_KEY"
}

params = {
    "latitude": "25.77",
    "longitude": "-80.19"
}

response = requests.get(url, headers=headers, params=params)
data = response.json()
print(data)

Why Choose RealtyAPI's /search_bycoordinates Endpoint

Built for developers who need reliable real estate data without the infrastructure overhead.

Real-Time Data Access

Get the most current /search_bycoordinates data from Vrbo without dealing with rate limits or IP blocks.

Simple Integration

Clear documentation and straightforward REST design make it easy to integrate this endpoint into any tech stack.

High Reliability

Our infrastructure ensures high uptime and consistent performance for your production applications.

Comprehensive Data

Access detailed /search_bycoordinates data through this carefully designed endpoint.

/search_bycoordinates Endpoint Use Cases

Real-world applications that leverage the /search_bycoordinates endpoint for Vrbo data.

Data Analysis

Analyze /search_bycoordinates data from Vrbo to gain insights and make data-driven decisions about real estate markets.

Market Monitoring

Monitor Vrbo /search_bycoordinates data to track changes, pricing trends, and market movements in real time.

Application Integration

Integrate /search_bycoordinates data from Vrbo into your web applications, mobile apps, or internal tools.

Workflow Automation

Automate data collection and processing workflows using Vrbo /search_bycoordinates data to improve team efficiency.

Reporting & Analytics

Generate reports and dashboards using Vrbo /search_bycoordinates data for stakeholders, investors, or clients.

Custom Solutions

Build custom real estate solutions that leverage Vrbo /search_bycoordinates data for your specific business needs.

Frequently Asked Questions

Common questions about the /search_bycoordinates endpoint.

Is the /search_bycoordinates endpoint official?

No, RealtyAPI provides an unofficial /search_bycoordinates endpoint that lets you access Vrbo data through our platform. We handle the complexities of data collection so you can focus on building your application.

How current is the data?

We provide real-time /search_bycoordinates data from Vrbo. When you make a request, we fetch the latest information available.

Can I use this endpoint in production?

Absolutely. Many businesses rely on RealtyAPI's endpoints for their production applications. Our infrastructure is designed for reliability and performance.

What happens if I exceed my API limit?

On paid plans, you can enable overage billing so your application keeps working. Free plan users can upgrade at any time to increase their quota.

Is there rate limiting?

Rate limits vary by plan. Free tier allows up to 10 requests per second. Paid plans offer higher limits suitable for production workloads.

What programming languages are supported?

RealtyAPI is a standard REST API, so it works with any language that can make HTTP requests: Python, JavaScript, Go, PHP, Ruby, Java, C#, and more.

Other Vrbo Endpoints

GET/details_byid GET/details_byurl GET/reviews_byid GET/host_details_byid GET/availability_byid GET/search_bylocation GET/search_bypolygon GET/search_byurl GET/autocomplete

Ready to Integrate the /search_bycoordinates Endpoint?

Get started with 250 free API calls. No credit card required.

Common Terms for /search_bycoordinates Endpoint Access

Vrbo /search_bycoordinates API integration/search_bycoordinates data APIAccess /search_bycoordinates data programmaticallyVrbo /search_bycoordinates API for developers/search_bycoordinates API endpoint/search_bycoordinates API documentationHow to use Vrbo /search_bycoordinates APIVrbo /search_bycoordinates API wrapper/search_bycoordinates real estate dataVrbo /search_bycoordinates REST API