Auction.com API
Search Auction.com

GET/search/bylocation

Auction.com /search/bylocation API

Build powerful real estate tools with RealtyAPI's /search/bylocation endpoint. Get Auction.com data programmatically without worrying about rate limits, IP blocks, or constantly breaking selectors. Our engineering team maintains the underlying infrastructure around the clock — monitoring for changes, optimizing request paths, and ensuring data accuracy — so you can treat real estate data as a reliable, always-available resource. The endpoint returns well-structured JSON with consistent field names and data types, making it straightforward to map responses to your application's data models. From solo developers to enterprise teams, thousands of customers trust this endpoint for their production data needs.

99.9% Uptime
|Real-Time Data|JSON Output

quick-start.py

import requests

url = "https://auction.realtyapi.io/search/bylocation"

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

params = {
    # Add parameters here
}

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

200 OK·application/json

Endpoint Reference

What You Can Do With
the /search/bylocation Endpoint.

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

Endpoint Parameters

21 params

Parameter	Type	Required	Description
`location`	STRING	Optional	City, county or ZIP — anything auction.com's autocomplete resolves, e.g. `Dallas, TX`, `Cook County, IL`, `60628`. The top suggestion wins; use [/autocomplete](https://realtyapi.io/dashboard?tab=playground&api=auction&endpoint=autocomplete) to preview matches. Omit for a nationwide search.
`page`	NUMBER	Optional	Page number of the result window (default `1`). Combine with `resultCount`. An explicit `offset` param is also accepted and overrides the page math.
`resultCount`	NUMBER	Optional	Results per page — default `50`, maximum `250` (aliases: `limit`, `pageSize`).
`sort`	ENUM	Optional	Sort order. Default `auction_date` — soonest auction first. `newest` / `oldest` sort by when the listing was activated, `price_low` / `price_high` by the auction starting bid, `distance` by proximity (only meaningful on [/search/bycoordinates](https://realtyapi.io/dashboard?tab=playground&api=auction&endpoint=searchbycoordinates)). Values: `auction_date, newest, oldest, price_low, price_high, distance`
`availability`	ENUM	Optional	Listing availability. `active` (default) = live & upcoming auctions currently on the marketplace. `removed` = closed/ended listings (sold, cancelled, or pulled from auction). Aliases accepted when calling directly: `closed`, `ended`, `sold`, `past`, `inactive` all map to `removed`. Values: `active, removed`
`buyingType`	ENUM	Optional	Buying type, using auction.com's own labels: `Foreclosure Homes` = trustee/courthouse foreclosure auctions (incl. pre-foreclosure), `REO Bank Owned` = bank-owned (REO) inventory, `Private Seller` = private-seller and short-sale listings, `Any` = no filter. Slug forms (`foreclosure`, `bank-owned`, `reo`, `private-seller`, `short-sale`) are accepted too. Matched client-side against each listing's `assetType` (see the scan-window note on the price filters). Tip: foreclosure inventory is courthouse-sale driven and thin in some states — browse foreclosure events on [/calendar](https://realtyapi.io/dashboard?tab=playground&api=auction&endpoint=calendar). Values: `Any, Foreclosure Homes, REO Bank Owned, Private Seller`
`assetType`	STRING	Optional	Finer-grained alternative to `buyingType`: a comma-separated list of asset-type enums — `FORECLOSURE`, `PRE_FORECLOSURE`, `BANK_OWNED`, `REO`, `PRIVATE_SELLER`, `SHORT_SALE`. Example: `FORECLOSURE,PRE_FORECLOSURE`. Client-side filter — applied over the first 250 listings fetched, so `total` reflects matches within that scan window.
`propertyType`	ENUM	Optional	Property structure type, matched client-side against the listing's `propertyType` / `propertyTypeGroup` (`house` covers all SINGLE_FAMILY variants, `condo` covers condominium units, `multi_family` covers multi-unit buildings). A comma-separated combination (e.g. `house,condo`) is accepted when calling the API directly. Client-side filter — applied over the first 250 listings fetched, so `total` reflects matches within that scan window. Values: `house, condo, townhouse, multi_family, mobile, land, commercial`
`minPrice`	NUMBER	Optional	Minimum price in USD. Price = the auction starting bid when available, otherwise the property valuation. Client-side filter — applied over the first 250 listings fetched, so `total` reflects matches within that scan window. Listings with no price data are excluded while a price filter is set.
`maxPrice`	NUMBER	Optional	Maximum price in USD — see `minPrice` for how the price is derived.
`minBeds`	NUMBER	Optional	Minimum bedrooms. Client-side filter — applied over the first 250 listings fetched, so `total` reflects matches within that scan window. Listings without bedroom data are excluded while set.
`maxBeds`	NUMBER	Optional	Maximum bedrooms (see `minBeds`).
`minBaths`	NUMBER	Optional	Minimum bathrooms. Client-side filter — applied over the first 250 listings fetched, so `total` reflects matches within that scan window. Listings without bathroom data are excluded while set.
`maxBaths`	NUMBER	Optional	Maximum bathrooms (see `minBaths`).
`minSqft`	NUMBER	Optional	Minimum living-area square footage. Client-side filter — applied over the first 250 listings fetched, so `total` reflects matches within that scan window. Listings without square-footage data are excluded while set.
`maxSqft`	NUMBER	Optional	Maximum living-area square footage (see `minSqft`).
`minYear`	NUMBER	Optional	Earliest year built. Client-side filter — applied over the first 250 listings fetched, so `total` reflects matches within that scan window. Listings without year-built data are excluded while set.
`maxYear`	NUMBER	Optional	Latest year built (see `minYear`).
`occupancy`	ENUM	Optional	Occupancy status — a key auction-buying differentiator (an `OCCUPIED` foreclosure needs eviction / leaseback diligence; `VACANT` usually allows faster possession). Server-side filter. Values: `OCCUPIED, VACANT, OWNER_OCCUPIED, TENANT_OCCUPIED, ADVERSELY_OCCUPIED`
`presale`	BOOLEAN	Optional	Set `true` to return only pre-foreclosure (presale) listings — properties scheduled for foreclosure that have not gone to auction yet.
`keywords`	STRING	Optional	Free-text search over listings (aliases: `search`, `query`, `q`).

JSON Response

Receive structured JSON containing /search/bylocation data from Auction.com. Parse it directly into your application models.

Real-Time Results

Every request fetches live Auction.com 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.

What You Can Build

/search/bylocation Endpoint Use Cases.

Real-world applications that leverage the /search/bylocation endpoint for Auction.com data.

Data Analysis

Analyze /search/bylocation data from Auction.com to gain insights and make data-driven decisions about real estate markets.

Market Monitoring

Monitor Auction.com /search/bylocation data to track changes, pricing trends, and market movements in real time.

Application Integration

Integrate /search/bylocation data from Auction.com into your web applications, mobile apps, or internal tools.

Workflow Automation

Automate data collection and processing workflows using Auction.com /search/bylocation data to improve team efficiency.

Reporting & Analytics

Generate reports and dashboards using Auction.com /search/bylocation data for stakeholders, investors, or clients.

Custom Solutions

Build custom real estate solutions that leverage Auction.com /search/bylocation data for your specific business needs.

Frequently Asked Questions

Common questions about the /search/bylocation endpoint.

Is the /search/bylocation endpoint official?

No, RealtyAPI provides an unofficial /search/bylocation endpoint that lets you access Auction.com 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/bylocation data from Auction.com. 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 Auction.com Endpoints

GET/details/byid GET/details/byurl GET/autocomplete GET/search/byzip GET/search/bycoordinates GET/search/byurl GET/calendar GET/calendar/event GET/states GET/enums GET/sell

No credit card required

Ready to integrate the
/search/bylocation endpoint?

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

Common Terms for /search/bylocation Endpoint Access

Auction.com /search/bylocation API integration/search/bylocation data APIAccess /search/bylocation data programmaticallyAuction.com /search/bylocation API for developers/search/bylocation API endpoint/search/bylocation API documentationHow to use Auction.com /search/bylocation APIAuction.com /search/bylocation API wrapper/search/bylocation real estate dataAuction.com /search/bylocation REST API

Auction.com /search/bylocation API

What You Can Do With
the /search/bylocation Endpoint.

Endpoint Parameters

JSON Response

Real-Time Results

Error Handling

Why Choose RealtyAPI's
/search/bylocation Endpoint.

Real-Time Data Access

Simple Integration

High Reliability

Comprehensive Data

/search/bylocation Endpoint Use Cases.

Data Analysis

Market Monitoring

Application Integration

Workflow Automation

Reporting & Analytics

Custom Solutions

Frequently Asked Questions

Other Auction.com Endpoints

Ready to integrate the
/search/bylocation endpoint?

Common Terms for /search/bylocation Endpoint Access

Auction.com /search/bylocation API

What You Can Do Withthe /search/bylocation Endpoint.

Endpoint Parameters

JSON Response

Real-Time Results

Error Handling

Why Choose RealtyAPI's/search/bylocation Endpoint.

Real-Time Data Access

Simple Integration

High Reliability

Comprehensive Data

/search/bylocation Endpoint Use Cases.

Data Analysis

Market Monitoring

Application Integration

Workflow Automation

Reporting & Analytics

Custom Solutions

Frequently Asked Questions

Other Auction.com Endpoints

Ready to integrate the/search/bylocation endpoint?

Common Terms for /search/bylocation Endpoint Access

What You Can Do With
the /search/bylocation Endpoint.

Why Choose RealtyAPI's
/search/bylocation Endpoint.

Ready to integrate the
/search/bylocation endpoint?