HiBid Scraper: Up to 1,000 Free Results a Month (2026)

Extract live and closed auction listings directly into 33 lot fields, including current bids, lot status, descriptions, and auctioneer identifiers. Filtering covers all 17 top-level categories and location filters for any US state/territory or Canadian province. Results land in your dataset for $5.00 per 1,000 results on the free plan. Built for buyers, market analysts, and resellers who need structured auction catalog data without managing browser automation. Not for teams trying to place bids, which requires a registered HiBid account.

Try it before you read further. Apify's free plan includes $5.00 of usage every month with no credit card, enough for up to 1,000 results at $0.005 each before platform usage. Open HiBid Scraper on Apify and run the prefilled example.

How reliable is HiBid Scraper in production?

Across the last 30 days of public runs on the Apify platform, HiBid Scraper recorded 74 runs with the following outcomes.

No run failed or timed out in the last 30 days. Keep a retry and an alert on scheduled runs all the same: a clean month is a record, not a guarantee.

What does it cost to run HiBid Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

Worked example: collecting 10,000 results costs $50.00 in result charges before run-start fees and platform usage. No run failed or timed out in the last 30 days, so the list price is a fair budget; keep a retry in place all the same.

The main driver of cost is the maxItems limit, as result billing applies directly to each dataset item written. Broad queries that return hundreds of records will consume dataset budget much faster than narrow ID lookups. Use small maxItems values on initial test runs to confirm field output before executing large category sweeps.

How do you run HiBid Scraper from the API?

The schema marks 1 of its 16 controls as required: mode. Every value in the payload below comes from the published schema's own prefills, which means you can paste it, swap the token, and get a real result.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~hibid-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"lots"}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "lots"
}

run = client.actor("crawlerbros~hibid-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "lots"
}

const run = await client.actor('crawlerbros~hibid-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

That endpoint blocks until the run completes. Fine while you are testing a handful of records, risky once a run takes minutes: a dropped connection loses the response even though the run itself finished. Switch to an asynchronous start with polling or a webhook before you schedule anything.

Which HiBid Scraper inputs matter, and which can you skip?

The mode selector determines which dataset schema is returned and is the single required input. Control the breadth of search queries using category, state, or searchText to avoid querying unnecessary records. Leave proxyConfiguration on AUTO for resilience, as no paid proxy group is required.

• mode (string): What to fetch. Default: "lots".
• searchText (string): Free-text keyword search (mode=lots/auctions). Searches titles and descriptions. Default: "tractor".
• category (string): Filter by top-level HiBid category (mode=lots/auctions). Default: "".
• state (string): Filter to auctions/lots located in a specific US state or Canadian province (mode=lots/auctions/auctioneers). Default: "".
• status (string): Filter by curated status (mode=lots/auctions). Default: "ALL".
• auctionType (string): Filter by bidding format (mode=lots/auctions). Default: "ALL".
• sortOrder (string): Sort order for lot results (mode=lots only). Default: "LOT_NUMBER".
• auctionIds (array): Scope lot search to one auction (mode=lots, first ID used), or look up full auction details (mode=auctionDetails, all IDs used). Find IDs in HiBid auction URLs, e.g. hibid.com/auction/755763/... → 755763. Default: [].
• lotIds (array): Look up specific lots by ID (mode=lotDetails). Find IDs in HiBid lot URLs, e.g. hibid.com/lot/307654532/... → 307654532. Default: [].
• auctioneerName (string): Filter auctioneers/auction houses by name (mode=auctioneers).
• zipCode (string): Center point for a distance radius search (mode=lots/auctions). Use with milesRadius.
• milesRadius (integer): Only include auctions/lots within this many miles of zipCode. Ignored if zipCode is empty. Default: 50.

The other 4 controls, with their defaults, are listed in the input schema on HiBid Scraper on Apify.

Fixed-choice controls: mode accepts lots (Search / browse lots (individual items)), auctions (Search / browse auctions (events)), lotDetails (Lookup specific lots by ID), auctionDetails (Lookup specific auctions by ID), auctioneers (Search auctioneers / auction houses); category accepts 18 values (default ""), including "" (Any category), 700001 (Antiques & Collectibles), 40089 (Art), 700006 (Cars & Vehicles); state accepts 76 values (default ""), including "" (Any state/province), AL (Alabama (US)), AK (Alaska (US)), AB (Alberta (CA)); status accepts ALL, HOT (most active), TOP (most bids/views), CLOSING (Closing soon), FEATURED, OPEN (currently biddable), CLOSED (ended); auctionType accepts ALL (All types), ONLINE (Online / timed only), BIDDABLE (live internet bidding), ABSENTEE (Absentee bidding), WEBCAST (live simulcast), LISTING (Listing only (no online bidding)); sortOrder accepts 19 values (default LOT_NUMBER), including LOT_NUMBER (Lot number), TIME_LEFT (Ending soonest), NEWLY_ADDED (Newly added), HOT_RANK (Hot rank).

What does HiBid Scraper return?

Dataset outputs contain structural listing data, full descriptions, item location, starting and current bid amounts, and direct links to HiBid. They omit empty fields entirely and contain only public catalog values available on listing pages.

Lots (mode=lots / lotDetails)

• lotId, lotNumber: Lot identifiers
• title, description: Item title and full description
• category, topCategory, categoryPath: Leaf category, top-level category, full breadcrumb
• currentBid, startingBid, bidCount: Bidding status
• buyNowPrice: Buy-it-now price, if offered
• status: OPEN, CLOSED, LIVE, SOLD, etc.
• timeLeft, timeLeftSeconds: Time remaining until close
• reserveSatisfied: Whether the reserve price has been met
• quantity, pictureCount: Item quantity and photo count
• shippingOffered: Whether the auctioneer offers shipping
• imageUrl, thumbnailUrl, images[]: Photo URLs
• auctionId, auctionTitle: Parent auction
• auctioneerName, auctioneerId: Auction house
• eventCity, eventState, eventZip, currency: Location & currency
• distanceMiles: Distance from the given ZIP, if a radius search was used
• sourceUrl: Canonical hibid.com/lot/... page
• recordType: "lot", scrapedAt

Auctions (mode=auctions / auctionDetails)

• auctionId, title, description: Auction identifiers
• auctioneerName, auctioneerId: Auction house
• eventAddress, eventCity, eventState, eventZip: Location
• eventDateBegin, eventDateEnd, bidOpenDateTime, bidCloseDateTime: Schedule
• lotCount, openLotCount, matchingLotCount: Lot counts
• bidType, auctionStatus: Bidding format and live status
• buyerPremium, currency: Terms
• shippingOffered, shippingType, isWebcast, isBiddable: Format flags
• imageUrl, thumbnailUrl: Featured photo
• distanceMiles: Distance from the given ZIP, if a radius search was used
• sourceUrl: Canonical hibid.com/auction/... page
• recordType: "auction", scrapedAt

Auctioneers (mode=auctioneers)

• auctioneerId, name: Auction house identifier and name
• address, city, state, postalCode, country: Location
• sourceUrl: Canonical hibid.com/auctioneer/... page
• recordType: "auctioneer", scrapedAt

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open HiBid Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Select lots in mode to focus on individual item extraction across independent auction houses.
2. Choose a top-level classification such as 700008 for Construction & Farm, or leave category empty to sweep all inventory.
3. Set state to a target US state or Canadian province, like TX, to limit geographically before running large jobs.
4. Select OPEN under status to avoid pulling archived records during live feed building.
5. Set maxItems to 50 for an initial dry run to verify schema consistency.
6. Execute the Actor and inspect the dataset to confirm fields like currentBid, sourceUrl, and auctioneerName are present.
7. Increase maxItems up to 2000 for your production schedules once the data schema fits your ingestion pipeline.

How do you apply it? Three worked playbooks

These are HiBid Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Auction aggregation

Outcome: Build a cross-auctioneer feed of open farm/equipment/estate lots

Configure: Set mode to "lots", category to "700008", status to "OPEN", sortOrder to "TIME_LEFT", and maxItems to 500.

Working method: Run the initial query across a specific high-value category. Confirm that returned items contain valid bidding telemetry and ending timestamps before expanding to additional top-level categories.

Deliverable: A structured JSON or CSV file containing item titles, high bid numbers, seller metadata, and direct lot links for live processing.

Stop condition: The returned record array is empty or contains closed lots when status is set to OPEN.

Use case 2: Price research

Outcome: Track current bids and closing prices for a category over time

Configure: Set mode to "lots", searchText to "John Deere", includeEnded to true, status to "CLOSED", and maxItems to 200.

Working method: Execute keyword-scoped historical queries across target categories. Extract bid progression, starting values, and final prices to construct time-series pricing curves.

Deliverable: A historical dataset of finished lots with closing prices, bid counts, and item descriptions suitable for valuation modeling.

Stop condition: Query execution fails or times out due to missing category, state, or search filters on archived data.

Use case 3: Auctioneer directory

Outcome: Build a directory of auction houses by region

Configure: Set mode to "auctioneers", state to "OH", and maxItems to 100.

Working method: Query regional directories state by state. Deduplicate auction house names, capture unique IDs, and aggregate complete mailing addresses.

Deliverable: A clean directory of active auctioneers containing names, IDs, full address metadata, and direct directory links.

Stop condition: Extracted records lack valid state codes or contain missing auctioneer IDs.

What breaks, and how do you design around it?

• Over the last 30 days, 0.0% of public runs failed and 0.0% timed out. Build retries and alerting around those rates rather than assuming every run completes.

When querying closed historical auctions, broad queries with no filters can time out on upstream servers. Always scope historical queries using category, state, or searchText when setting includeEnded to true. If an auctioneer miscategorizes a lot at listing time, rely on keyword matching across description fields rather than category filters alone.

When should you not use HiBid Scraper?

Do not use this Actor if you need to place bids on listings; placing a bid requires a HiBid account, and this tool only reads public listing data. If your dataset demands specialized heavy equipment coverage from dedicated regional market platforms rather than grassroots estate auctioneers, use Purple Wave Auction Scraper or TractorHouse Scraper instead. For fine art, high-value collectibles, and luxury estates, consider Doyle Auctions Scraper or Heritage Auctions Scraper.

What should you check before trusting the output?

• Verify that sourceUrl begins with hibid.com/lot/ for lot records or hibid.com/auction/ for auction records.
• Check that numeric fields like currentBid and bidCount do not return as null on active lots.
• Ensure status values match expected states like OPEN or CLOSED when executing status-filtered runs.
• Abort scheduled runs if record count hits 0 unexpectedly when searching active categories with status set to OPEN.
• Confirm that currency matches local expectations when targeting Canadian provinces versus US states.

None of this proves a record is correct. It gives a scheduled HiBid Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

How much does running this Actor cost?

Results cost $0.005 per result, which is $5.00 per 1,000 results on the free plan. Apify's free plan includes $5.00 of monthly usage with no credit card, covering up to 1,000 results of this Actor. Apify bills platform usage separately for each run on top of result charges.

Do I need proxies or account cookies to run this?

No. Browsing and searching auctions or lots on HiBid is fully public. No account, login credentials, or paid proxy group is required. The default AUTO proxy setting handles requests out of the box.

Can I target specific auctions or lots directly?

Yes. Set mode to lotDetails and provide target lot IDs in the lotIds list, or set mode to auctionDetails and supply auction IDs in the auctionIds field to perform direct lookups.

Why did my closed auction search return no items?

Unfiltered historical queries across the entire HiBid archive can time out on HiBid's upstream servers due to dataset size. Narrow your historical searches by adding a category, state, or free-text keyword alongside includeEnded.

Are Canadian auctions covered alongside US listings?

Yes. The state selector includes all Canadian provinces in addition to US states and territories, matching HiBid's native geographic coverage across North America.

Where to go next

When you are ready to run it, open HiBid Scraper on Apify; the free plan covers up to 1,000 results a month.

Start with the HiBid Scraper Actor page for the current input schema, pricing tier, and run history.

Other Actors we maintain for related data:

• AuctionZip Auction & Auctioneer Directory Scraper: Scrape AuctionZip.com - search live and upcoming auctions by keyword, category or zip code, browse auctions by US state, or pull an auctioneer's current listings.
• Heritage Auctions Scraper: Scrape Heritage Auctions (ha.com) - the world's largest collectibles auctioneer.
• Purple Wave Auction Scraper: Scrape Purple Wave (purplewave.com) farm, construction, and truck/trailer equipment auctions.
• Fastline Scraper: Scrape Fastline.com - a leading US farm equipment marketplace.
• Doyle Auctions Scraper: Scrape Doyle Auctions (doyle.com) - one of the world's leading fine art, jewelry, silver, coins, and decorative arts auction houses.
• Auction.com Property Scraper: Scrape residential real estate auction listings from auction.com with bank-owned, foreclosure, and private-seller properties across all 50 US states.
• EstateSales.net Estate & Moving Sale Listings Scraper: Scrape EstateSales.net - search estate, moving, and auction sale listings by US state, city or ZIP code, filter by real sale type and date range, or pull the site's nationally-featured sales.
• TractorHouse Scraper: Scrape TractorHouse.com farm equipment, tractors, construction machinery, trailers, and trucks.

Related guides:

• Heritage Auctions Scraper: 20 Data Fields per Record (2026)
• 1stDibs Scraper: 24 Data Fields, Up to 1,000 Free Results/Month (2026)
• GovDeals Scraper: Practical Guide for Surplus Auction Sourcing
• Etuovi.com Real Estate Scraper: 44 Data Fields per Record (2026)

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-30.

• Actor last updated by its maintainers on 2026-07-04.

• Run outcome figures cover the 30 day public window ending 2026-09-30.

• HiBid Scraper on Apify