eAuctions India APIeauctionsindia.com ↗
Access property auction listings, live auctions, and detailed specs from eauctionsindia.com. Filter by state, city, or keyword across 4 endpoints.
What is the eAuctions India API?
The eAuctions India API provides 4 endpoints to search, browse, and retrieve structured data from eauctionsindia.com's property auction database. The search endpoint accepts keyword, state, and city filters to return paginated auction listings, while details returns field-level data for a specific auction including reserve price, earnest money deposit, bank info, and start and end timestamps.
curl -X GET 'https://api.parse.bot/scraper/1de86bbb-e71d-4190-88a3-af1a15fb1328/search?page=1&state=maharashtra&keyword=780269' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace eauctionsindia-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: eAuctions India SDK — search auctions, fetch details, filter by state."""
from parse_apis.eauctions_india_api import EAuctionsIndia, State, AuctionNotFound
client = EAuctionsIndia()
# List live auctions — capped to 5 items
for auction in client.auctionsummaries.live(limit=5):
print(auction.title, auction.reserve_price, auction.date)
# Search auctions filtered by state using the State enum
for auction in client.auctionsummaries.search(state=State.MAHARASHTRA, limit=3):
print(auction.id, auction.title, auction.reserve_price)
# Drill into a single auction's full details via the summary
summary = client.auctionsummaries.live(limit=1).first()
if summary:
detail = summary.details()
print(detail.title, detail.reserve_price, detail.emd)
print(detail.location.state, detail.location.city, detail.location.area)
print(detail.bank_info.bank_name, detail.property_details.property_type)
# Fetch available filter options (states and cities)
filters = client.filteroptionses.get()
for state in filters.states[:3]:
print(state.id, state.name)
# Fetch auction details directly by ID with typed error handling
try:
auction = client.auctions.get(auction_id="780269")
print(auction.title, auction.status, auction.start_date)
except AuctionNotFound as exc:
print(f"Auction not found: {exc.auction_id}")
print("exercised: auctionsummaries.live / auctionsummaries.search / summary.details / filteroptionses.get / auctions.get")
Search for auctions with optional filters for auction ID, state, and city. Returns paginated listing results. When no filters are provided, returns the latest upcoming auctions. Pagination via page number in the URL path.
| Param | Type | Description |
|---|---|---|
| city | string | City slug to filter by, as returned by the metadata endpoint |
| page | integer | Page number for pagination (1-based) |
| state | string | State slug to filter by, as returned by the metadata endpoint (e.g. 'gujarat', 'maharashtra') |
| keyword | string | Auction ID to search for (numeric string, e.g. '780269') |
{
"type": "object",
"fields": {
"items": "array of auction listing objects with id, url, title, date, reserve_price, location, and category",
"total_on_page": "integer count of items returned on this page"
},
"sample": {
"data": {
"items": [
{
"id": "787499",
"url": "https://www.eauctionsindia.com/properties/787499",
"date": "",
"title": "eAuction Car in Vellore, Vellore",
"category": "",
"location": "",
"reserve_price": "₹2,70,000.00"
}
],
"total_on_page": 1
},
"status": "success"
}
}About the eAuctions India API
Endpoints and Data Coverage
The API covers four operations against eauctionsindia.com's auction inventory. The search endpoint accepts optional keyword, state, and city parameters — state and city values must be slugs as returned by the metadata endpoint (e.g. gujarat, maharashtra). Results come back as paginated arrays of auction listing objects, each carrying an id, url, title, date, reserve_price, location, and category. When called with no filters, it returns the latest upcoming auctions.
Live and Detailed Auction Data
The live endpoint requires no inputs and returns all currently active or imminently upcoming auctions in the same listing object shape as search. For deeper data, the details endpoint takes a numeric auction_id and returns a richer object: emd (earnest money deposit amount), images array, start_date, end_time, status (one of Upcoming, Active, Closed, or Unknown), a location object broken into state, city, and area, and a bank_info object with bank_name, branch_name, and service_provider.
Metadata for Filter Values
The metadata endpoint returns the full set of states and cities available as filter slugs, each with an id and name. This makes it straightforward to build dropdown menus or enumerated filter sets without hardcoding slug values. State slugs from this endpoint are the accepted inputs for the state parameter in search, and the same applies to city slugs.
The eAuctions India API is a managed, monitored endpoint for eauctionsindia.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when eauctionsindia.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official eauctionsindia.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor newly listed bank auction properties across a specific state using the
searchendpoint with astateslug - Track live auctions in real time by polling the
liveendpoint for active and imminent listings - Retrieve earnest money deposit and reserve price for a known auction via the
detailsendpoint to assess bid eligibility - Build a property auction alert system by storing
auction_idvalues and checking status changes using thedetailsendpoint - Aggregate auction listings by category (plot, land, flat) using the
keywordfilter insearch - Populate a city/state filter UI by fetching available slugs from the
metadataendpoint - Identify the originating bank branch and service provider for an auctioned asset via
bank_infoin thedetailsresponse
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does eauctionsindia.com have an official developer API?+
What does the `details` endpoint return beyond what `search` provides?+
details endpoint returns several fields absent from listing results: emd (earnest money deposit), an images array, start_date, end_time, a status field (Upcoming, Active, Closed, or Unknown), a structured location object with state, city, and area, and a bank_info object with bank name, branch name, and service provider.Can I retrieve bid history or current highest bid for an auction?+
details endpoint, but does not expose bid history, current bid amounts, or bidder counts. You can fork this API on Parse and revise it to add an endpoint targeting that data if it becomes available on the source page.How does pagination work in the `search` endpoint?+
search endpoint accepts an integer page parameter. Each response includes a total_on_page count reflecting items on that page. There is no total-results-count or total-pages field in the response, so iterating requires checking whether total_on_page drops to zero to detect the last page.