America's biggest used camera store, as JSON: the grade, the stock count and the price

It is KEH's own catalogue price, and we measured exactly what it means rather than assuming. KEH's catalogue index carries ONE price per product while a product page offers several condition grades at several prices, and checked against KEH's own pages the index price is the CHEAPEST grade's: the Canon EOS R6 body indexed at 1,352.00 is offered at 1,352 Excellent, 1,469 Excellent Plus and 1,527 Like New Minus. So the API publishes that figure twice — price, which is what KEH's listing shows, and price_from, which says what it means — and publishes grades_available so you can see which grades exist. The per-grade prices are not on this surface and per_grade_prices_available says so. The index also publishes a price_range field, and that field is a fake: it was [price, price] on all 1,600 rows we sampled, so it is returned only as price_range_index beside price_range_is_grade_blind rather than passed off as a grade ladder. All prices are plain US dollars; 1352.0 is 1,352.00 dollars, not cents.

Because 46,946 of KEH's 54,499 indexed products are sold out, and on a sold-out record the price left in the index is stale and the grade is gone. One measured example: a Leica M6 indexed at 1,266.00 with no grade, while KEH's own page still showed a Bargain copy at 3,200.00. Returning those by default would make 86 percent of every result set unbuyable and some of it wrong. So in_stock defaults to true, every row carries units_in_stock and price_is_live_offer, and you can pass in_stock=any or in_stock=false to get the sold-out records deliberately — they are genuinely useful as a what-KEH-handles list and as price history, as long as you know which they are.

The API returns units_in_stock, KEH's own unit count, and we checked that it is a real number rather than a figure that saturates at a round cap. Over 800 rows: with the in-stock filter the minimum is 1 and 0 never appears once, without it 0 is the single most common value, and there are 83 distinct counts with a maximum of 264 and no clustering at any ceiling. 0 and 'in stock' never occur together. The product page that would corroborate the number is behind KEH's own bot protection, so this is KEH's figure as KEH publishes it, and that is said rather than glossed over.

Every response carries meta.total_results, KEH's own match count for your exact request, plus meta.filters_applied. More than that: all 25 filters were verified by asking KEH's facet block what a value should count and then re-querying that value as a filter — 25 of 25 matched exactly, including the long tail, where a lens mount with exactly one product returned exactly one. Against the 7,553 in-stock products in one run: Canon 783, Canon plus Nikon 1,688 (the exact sum, because values on one field are OR-ed), Bargain grade 1,892, Full Frame 35mm 2,034, Canon EF mount 437, prime lenses 1,897, autofocus with a lens motor 1,457, telephoto 593, f/2.8 589, camera bodies 656, Overstock 1,538, over 2,000 dollars 299, under 50 dollars 2,762, reaching past 400 mm 68. Different fields are AND-ed: Canon plus Excellent grade is 562 against 2,983 and 4,218. Two things the source does silently and the API refuses to: an unknown filter value returns zero rows rather than an error, and an unknown sort is ignored and the unsorted order handed back — so the API validates both itself and tells you.

Call facets. It returns KEH's own live taxonomy — 25 of them, every brand, grade, category, system, gear type, lens mount, format, aperture, filter size and type, card type, flash system, optical design and intended use that has stock right now, each with KEH's own count, plus the price and focal-length ranges as real numeric spans. Every value it returns is a value search accepts, and it takes the same filters as search, so you can ask for the taxonomy inside a scope: the lens mounts available under Fujifilm came back as 9 values with counts. It also marks five values filterable: false — those are values KEH's own taxonomy advertises but cannot filter on, because their labels carry a stray trailing space in KEH's data and match zero products whichever way they are spelled. The API refuses those with that explanation instead of handing you an empty success.

Yes, and the categories action gives you the map first: 135 nodes with their id, name, parent, readable breadcrumb and live product count, deepest counts first — Used Camera Lenses 15,795, Accessories 18,390, Used SLR and DSLR Lenses 9,939, Used Cameras 9,248, Used Film Cameras 4,948, Tripods and Supports 4,692. The ids it returns are exactly what the category filter takes, and a parent id includes its children. Pass it any search filter and you get the tree within that scope, which answers questions a flat listing cannot: which categories hold Leica gear came back as 58 of the 135.

Film is a first-class part of this catalogue and of this API. KEH holds 4,948 used film cameras and 2,915 large-format items, and film-specific attributes are their own filters: film_type covers 35mm roll (2,633), 120 roll (278), 220 roll, 4x5 through 11x14 sheet, Instax, APS, 110 and 126 cartridges, 8mm, 16mm and Super 8. Coverage format runs from Full Frame 35mm down to 8x10 inch and up through medium format. Flash system covers the film-era TTL protocols by name — Canon A-TTL, Minolta TTL, Hasselblad TTL pre-flash and 18 more — which is exactly what you need to match an old flash to an old body.

Which of KEH's grades it currently holds of that model, ranked best to worst; the full spec sheet as KEH's own catalogue describes it — system, gear type, coverage format, lens mount, megapixels, film type, filter thread and type, prime or zoom, focus type, maximum aperture, focal-length range, memory-card types, special optical design, TTL flash system and intended uses; the category breadcrumb; KEH's merchandising tags; the unit count; and the cleaned description. You can call it with KEH's product id or by pasting a keh.com product URL. A product id KEH does not index answers NOT_FOUND, not an empty success.

No, and that is the nature of this source rather than something removed. KEH buys the gear, inspects and grades it and sells it itself, so there is no third-party merchant, seller profile or seller rating anywhere on the page — the warranty and the grade are KEH's own. Nothing is masked here; there is simply no seller entity to publish.

To 10,200 rows per query, and the API tells you rather than letting you find out. That is KEH's search service's own hard cap — at most 200 rows per call and a start offset of at most 10,000, which it states in its own refusal — so meta.pagination carries depth_limit, reachable_results and depth_limit_reached, and asking past the cap is refused as an invalid parameter before a request is spent, with the advice to split the query by category, brand or price band. Paging itself is honest: pages one, two and three at 50 rows had zero overlapping products in either direction, so there is no silent repeat of the last page.

You get rows, and you should know that before you trust a long-tail query. KEH's search relaxes instead of answering empty: zzqqxxnotathingqq returned 1,217 products, qwertyasdfzxcv 870, a three-word nonsense phrase 4. The relevance score does not separate that fallback from a real hit (520.9 against 505.3) and KEH's own precision metadata reports the identical value in both cases, so there is no honest flag for us to compute and we do not invent one — it is stated on the query parameter and repeated in meta.notes, and the fix is to call suggest first so a keyword lands on gear KEH actually carries. A precise model name is exact: canon eos r6 returned 157, canon eos r6 mark ii black body 13, hasselblad 503cw 293.

KEH API is a ReefAPI endpoint group for used cameras, lenses and film gear from keh.com as json: 54,000 products, 7,500 in stock, with keh's own condition grades, 25 measured filters and the live us price. It returns live JSON through POST requests under /keh/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. KEH calls use the same shared credit balance as every other ReefAPI engine.

No login to KEH 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.