Every heavy equipment auction on Equipment Facts, one row each
Equipment Facts API returns live Equipment Facts data as clean JSON for heavy equipment auctions in the us and canada: auctions, lots, specs and live bids.
- endpoints
- 5
- credit per call
- 1
1 credit per call≈ $1/1,000 calls1,000 free credits, no card
5 active endpoints. Every call is 1 credit.
- POST/equipmentfacts/v1/auctions1 credit
- POST/equipmentfacts/v1/lots1 credit
- POST/equipmentfacts/v1/lot1 credit
- POST/equipmentfacts/v1/search1 credit
- POST/equipmentfacts/v1/filters1 credit
Run the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Equipment Facts API
3 of 5 endpoints, ready to run
One row per auction: title, auctioneer with phone and website, online or on-site, bidding format, start and end time in UTC next to the time the site shows, status, full address, description, equipment types, lot count for online sales, catalogue and bidding links. 25 per page with the site's own total.
// 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.
What Equipment Facts endpoints does ReefAPI ship?
5 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Every parameter, every allowed value →
Missing a Equipment Facts endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Equipment Facts API works
Equipment Facts 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 632 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 nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Track upcoming heavy equipment auctions and the lots you care about
The auction list first, then the catalogues that matter, then the lots you want to follow.
{"page": 1}25 auctions a page with auctioneer, date, type and address; page through to the site's own total.
{"auction_id": "<auction_id from a row>"}Every lot with year, make, model, hours and the live bid.
{"query": "excavator", "year_min": 2015, "state": "TX"}The same lot rows across every auction.
A dated, located list of equipment auctions and a priced view of the machines you follow.
curl -X POST https://api.reefapi.com/equipmentfacts/v1/auctions \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"page":1}'{
"ok": true,
"data": { … },
"meta": {
"api": "equipmentfacts",
"endpoint": "auctions",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What the source gives, what it hides, and what we checked
Measured on 2026-11-12: 74 live calls across all five actions plus 7 deliberate bad inputs, checked against the site's own counts and pages.
Upcoming auctions came back as 629, the total the site prints; the online and on-site counts and the state, date and category totals equal the site's own filter counts.
The site lists two online sales twice with every field identical. Each comes back once and duplicates_removed says how many were dropped; total_results stays the site's own number.
One online sale's lots across its pages came to 30, the same as its total and the lot count on the auction row. For 6 lots the title, photo count, hours and bids matched the lot page.
starts_at is UTC; the time and zone the card shows come back beside it. All 627 distinct upcoming auctions agreed.
Past auctions show sale prices only to signed-in users, so sold_price is null rather than the last bid presented as a price.
The site does not publish how many pre-bids an on-site lot has, so bid_count is null there; online sales carry it.
The site's relevance order repeats and skips lots from page to page, so search pages by recently added by default (336 of 336 lots reached); relevance can still be asked for.
What people build with Equipment Facts
The jobs this data is most often used for.
endpoints
credit per call
Price-intelligence teams use Equipment Facts to get every upcoming (or past) auction on Equipment Facts, one clean row per auction.
Classifieds aggregators use Equipment Facts to get the lots (equipment items) of one Equipment Facts auction.
Resale and arbitrage tools use Equipment Facts to get one lot in full.
Lead-generation teams use Equipment Facts to search lots across every Equipment Facts auction by keyword, manufacturer, category, year ran….
What Equipment Facts 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.
- 1,000 free credits on signup, no card
- One key, all 632 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/equipmentfacts/v1/auctions \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"page":1}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/equipmentfacts/v1/auctions",
headers={"x-api-key": REEF_KEY},
json={
"page": 1
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Equipment Facts.
What is the Equipment Facts API?▾
Equipment Facts API is a ReefAPI endpoint group for heavy equipment auctions in the us and canada: auctions, lots, specs and live bids. It returns live JSON through POST requests under /equipmentfacts/v1.
Is the Equipment Facts API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Equipment Facts calls use the same shared credit balance as every other ReefAPI engine.
Do I need an Equipment Facts login or account?▾
No login to Equipment Facts 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 Equipment Facts data?▾
The page example is captured from a live auctions call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Equipment Facts API use?▾
Equipment Facts actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Equipment Facts from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call equipmentfacts actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Equipment Facts API an Equipment Facts scraper?▾
It is the managed alternative to a DIY Equipment Facts scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same heavy equipment auctions in the us and canada: auctions, lots, specs and live bids back as clean JSON.
Why does my Equipment Facts scraper keep getting blocked?▾
Most Equipment Facts scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked calls are free.
116 Classifieds & Second-hand APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Equipment Facts, 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 631 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-11-12.