US online auctions, with the hammer price kept apart from the last online bid
The Proxibid API turns proxibid.com, a US marketplace where hundreds of auction houses run live webcast and timed online sales, into JSON in seven actions.
7 active endpoints, on 1, 2 and 3 credit tiers.
- POST/proxibid/v1/search
- POST/proxibid/v1/sold
- POST/proxibid/v1/auctions
- POST/proxibid/v1/sellers
- POST/proxibid/v1/catalog
- POST/proxibid/v1/detail
- POST/proxibid/v1/lot_status
What Proxibid endpoints does ReefAPI ship?
7 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Proxibid API
3 of 7 endpoints, ready to run
Open and upcoming lots by keyword or category path, with sale type, state and auction house, and the source's own match count.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Proxibid API works
Proxibid is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 491 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Price a machine from real auction results
Two calls per comparable. The archive finds the lots, the status call gives the price they actually sold for.
Closed lots for the model with their last online bid, sale type and date (5,382 matches on the day we measured). Timed-sale rows already carry the final price.
hammer_price and sold_to for the lot. On live webcast sales this is the number to use: it differed from the archive figure on every live lot we checked.
A comparable set of realised prices, with floor and online sales told apart.
curl -X POST https://api.reefapi.com/proxibid/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"excavator"}'{
"ok": true,
"data": { … },
"meta": {
"api": "proxibid",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}One closed lot, two prices that do not agree
Lot 102551528, an excavator in a live webcast sale on 2026-08-22, read on 2026-10-14. The archive and the lot's own feed publish two different figures. This is what each one means and what the API returns.
| where at the source | value | what the API does with it |
|---|---|---|
| closed-lot archive search | $550 | sold row: last_online_bid = 550, hammer_price = null |
| lot record behind the closed page | $550 (not shown on the page) | detail: page_price = 550 |
| the lot's bid feed: next bid | $600 | the archive figure plus one increment |
| the lot's bid feed: hammer price, buyer | $11,000, on site | detail / lot_status: hammer_price = 11000, sold_to = floor, price_mismatch = true |
On live webcast sales the archive keeps the last online bid, not the price the lot sold for: it differed from the hammer price on every live lot we checked (19 of 19, then 5 of 5). On timed online sales the two were equal (6 of 6, then 10 of 10).
What the source publishes, measured
Measured on 2026-10-14 against the live site: 250 search rows from five categories, 9 lot records, 25 archive rows and their bid feeds.
Keyword and category search; 'tractor' 3,490 open lots, heavy construction equipment 30,813 by facet count.
Current bid matched the lot's own bid feed on 12 of 12 rows and 9 of 9 lot records; unbid lots 8 of 8.
Closed lots back to 2010. The price is the last online bid: equal to the hammer on 16 of 16 timed lots, different on 24 of 24 live lots.
From detail or lot_status, with sold_to floor or internet.
The first 10,000 matches of any query; the count stops at 10,000 and total_from_facets gives the real size.
Timed lots: ends_at within two minutes of the source's countdown, 8 of 8. Live lots: no end time at source.
Bid history; the bid count on the lot page; state and coordinates on search rows (the auction record has them).
What people build with Proxibid
The jobs this data is most often used for.
endpoints
credits per call
Equipment valuation: search the closed-lot archive for a model, then read lot_status on the live-sale rows to get the hammer price instead of the last online bid.
Auction monitoring: poll lot_status every few minutes for the lots you follow; it returns the high bid, next bid, seconds left, reserve state and extended-bidding flag in about half a kilobyte.
Deal flow by region: search a category path in one state, sorted by soonest closing, and read each lot's location, buyer's premium and pickup terms.
Auction-house coverage: find houses with sellers, list their upcoming sales with auctions, and read each catalogue with its current and opening bids.
What Proxibid data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 491 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/proxibid/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"excavator"}'import requests
r = requests.post(
"https://api.reefapi.com/proxibid/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "excavator"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Proxibid.
Get a free key →Is the archive price the price the lot sold for?▾
Only on timed online sales. On live webcast sales the lot is hammered in the room and the archive keeps the highest online bid, which was lower than the hammer price on every live lot we checked. So sold rows carry last_online_bid, and the hammer price comes from detail or lot_status (hammer_price, with sold_to floor or internet). lot_status costs one credit and is about half a kilobyte.
What does price_is mean on a row?▾
Which number you are looking at. current_bid means bids have been placed. opening_bid means no one has bid and the house set a starting price (4 of 17 unbid rows in one sample). none means neither. A lot with no bids never shows its opening price as a current bid.
Why do live lots have no end time?▾
Because the source does not publish one. A lot in a live webcast sale closes when the auctioneer reaches it, so ends_at is null and sale_starts_at carries the sale start; detail adds the lot's place in the running order (for example 359 of 687). Timed lots carry ends_at, and it matched the source's own countdown within two minutes on 8 of 8 lots.
How many results can one search return?▾
The source serves at most the first 10,000 matches of any query, and its match count stops at 10,000 too. When that happens total_capped is true and total_from_facets carries the real size from the facet counts (heavy construction equipment: 10,000 shown, 30,813 by facets). Narrow with a category path, a sale type or a state; each response lists the next category paths with their counts.
Which filters work?▾
Every one was measured against an unfiltered control in the same run. Open lots for 'tractor': 3,490, of which 1,760 in farm equipment, 2,898 live and 592 timed, 441 in Pennsylvania and 415 in Texas; the state was confirmed on the lot record 8 of 8 times. Auctions for 'excavator': 61, of which 15 timed, 46 live, 2 in Ohio. The auction house name must be written exactly as the source writes it.
Is the high bidder's name returned?▾
As the source shows it, which is masked, for example i****k. After the sale, sold_to says whether the lot went to a bidder in the room or online, and winning_bidder carries the masked online name when there is one.
What is not available?▾
Bid history is not published on the public lot page, so it is not returned. The bid count is in search and catalogue rows, not on the lot page. Lot rows in search carry no state or coordinates (the source leaves them empty); the auction record has the full address and coordinates.
How fast is it?▾
Over two back-to-back runs of the final code every one of 52 successful-path calls succeeded. Median: search 0.9 to 1.0 s, sold 1.2 to 1.4 s, auctions 0.9 s, lot_status 0.9 to 1.0 s, catalog 1.7 to 1.8 s, detail 2.7 to 3.1 s; the slowest call in either run took 4.0 s.
What is the Proxibid API?▾
Proxibid API is a ReefAPI endpoint group for us online auctions as json: open lots with current and opening bids, the closed-lot archive, auction catalogues, and every lot's outcome with the hammer price and whether a floor or an online bidder won. It returns live JSON through POST requests under /proxibid/v1.
Is the Proxibid API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Proxibid calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Proxibid login or account?▾
No login to Proxibid is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Proxibid data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Proxibid API use?▾
Proxibid actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Proxibid from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call proxibid actions with the same key, credit pool and JSON envelope used by normal REST requests.
231 E-commerce & Marketplaces APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Proxibid, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 490 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-10-14.