Discover/Clean Sweep Auctions API
live

Clean Sweep Auctions APImarketplace.cleansweepauctions.com ↗

Search active, completed, and fixed-price lots on Clean Sweep Auctions. Get bid counts, next-bid amounts, grades, and sale prices via 2 endpoints.

Endpoint health
verified 3h ago
search_lots
get_lot
2/2 passing latest checkself-healing
Endpoints
2
Updated
3h ago

What is the Clean Sweep Auctions API?

The Clean Sweep Auctions Marketplace API gives programmatic access to auction and fixed-price listings across the site's three listing pools using 2 endpoints. The search_lots endpoint accepts keyword queries and a status filter to target active auctions, recently closed lots, or store inventory, returning up to 20 results per page with pagination support. The get_lot endpoint delivers per-lot economics including current bid amount, bid count, grade, grader, and listing status.

This call costs1 credit / call— charged only on success
Try it
1-based page number; each page holds up to 20 lots. Omitted = first page.
Result ordering, using the site's sort options.
Keyword(s) to search for in listing titles/descriptions; all keywords must match.
Which listing pool to search: active auction lots, completed (recently closed) auction lots, or fixed_price online-store listings.
→ api.parse.bot/scraper/64d6f3af-b59f-4ce7-a4f1-7c938dd39538/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/64d6f3af-b59f-4ce7-a4f1-7c938dd39538/search_lots?sort=price&query=mantle&status=active' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 2 totalmissing one? ·

Keyword search over the marketplace listings. One round trip per call; results are returned in pages of 20 lots (page 1 when page is omitted) and has_more says whether a further page exists. The status filter selects one of three independent listing pools the site exposes: active auction lots (default), recently closed auction lots, or fixed-price online-store listings; the pools are never mixed. Each row carries the site's own lot id, lot number (auction lots only; null for store items), title, URL, listing status as displayed (active, ended, or fixed_price), and only the money figures the listing page shows: current_bid and next_bid for auction lots (for ended lots this is the last bid shown, not a final sale price), asking_price for fixed-price items. currency is USD when the site displays a $ figure for the row, otherwise null. Grading fields are read from the title text only: condition_text is the raw text after 'Cond:' when present; grader, grade and grade_qualifier are filled only when a recognised grading company code (PSA, SGC, BGS, BVG, BCCG, CSG, CGC, GAI, KSA, HGA, TAG, ISA, ACE, MNT) with a numeric or A/AA/Auth grade appears, and grade_qualifier only when an explicit PSA/SGC qualifier (MC, OC, ST, MK, PD, OF) follows the grade. Nothing is inferred: missing values are null. Optional sort accepts the site's own sort codes. A query with no matches is a valid empty result (lots is an empty array).

Input
ParamTypeDescription
pageinteger1-based page number; each page holds up to 20 lots. Omitted = first page.
sortstringResult ordering, using the site's sort options.
queryrequiredstringKeyword(s) to search for in listing titles/descriptions; all keywords must match.
statusstringWhich listing pool to search: active auction lots, completed (recently closed) auction lots, or fixed_price online-store listings.
Response
{
  "type": "object",
  "fields": {
    "lots": "array of lot rows: lot_id (string, site item id), lot_number (string or null), title, url, listing_type (auction|fixed_price), status (active|ended|fixed_price), current_bid, next_bid, asking_price (numbers or null), currency (USD or null), time_remaining_text (site countdown text, active auction lots only), condition_text, grader, grade, grade_qualifier (strings or null)",
    "page": "1-based page number returned",
    "query": "echo of the search keywords",
    "has_more": "boolean: true when a further page of results exists",
    "page_size": "maximum lots per page (20)",
    "status_filter": "the listing pool searched (active, completed, fixed_price)"
  },
  "sample": {
    "data": {
      "lots": [
        {
          "url": "https://marketplace.cleansweepauctions.com/item-902361/",
          "grade": "7",
          "title": "Lot #447 1958 Topps # 418 Mantle/Aaron Cond: PSA 7",
          "grader": "PSA",
          "lot_id": "902361",
          "status": "active",
          "currency": "USD",
          "next_bid": 660,
          "lot_number": "447",
          "current_bid": 600,
          "asking_price": null,
          "listing_type": "auction",
          "condition_text": "PSA 7",
          "grade_qualifier": null,
          "time_remaining_text": "Ends in 14d 12h 7m +"
        }
      ],
      "page": 1,
      "query": "mantle",
      "has_more": true,
      "page_size": 20,
      "status_filter": "active"
    },
    "status": "success"
  }
}

About the Clean Sweep Auctions API

What the API Covers

The API exposes Clean Sweep Auctions' marketplace inventory through two endpoints. search_lots accepts a required query string and an optional status parameter that selects one of three independent listing pools: active (open auctions), completed (recently closed auctions), or fixed_price (store listings). Results arrive in pages of 20 lots, each row carrying lot_id, lot_number, title, url, listing_type, and status metadata. The has_more boolean tells you whether a subsequent page exists, and the page parameter lets you step through results.

Lot Detail Fields

get_lot accepts either the numeric lot_id or the full lot URL as emitted by search_lots. The response includes the lot's identity fields (lot_id, inventory_id, lot_number, title, url), its status (active, ended, or fixed_price), and pricing data. For auction lots, next_bid carries the next valid bid amount (null once bidding closes) and bid_count reports the number of bids placed. Where the site prints a grade, grade and grader are populated; both are null when no grading information is present. listed_at provides an ISO-8601 timestamp with UTC offset when available, and currency is set to USD whenever dollar figures appear.

Pagination and Filtering

Every search_lots call targets exactly one listing pool per request — there is no single call that spans all three pools simultaneously. Page 1 is returned when the page parameter is omitted. The optional sort parameter maps to the ordering options the site exposes natively. Because page_size is fixed at 20, iterating large result sets requires sequential page increments guided by has_more.

Reliability & maintenanceVerified

The Clean Sweep Auctions API is a managed, monitored endpoint for marketplace.cleansweepauctions.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when marketplace.cleansweepauctions.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 marketplace.cleansweepauctions.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.

Last verified
3h ago
Latest check
2/2 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Track bid counts and next-bid prices on active Clean Sweep auction lots for a price-alert tool
  • Pull recently closed lot prices via the completed status filter to build a realized-price database for collectibles
  • Compare fixed-price store listings against auction closing prices using listing_type from search results
  • Aggregate graded card or collectible data using the grade and grader fields returned by get_lot
  • Monitor new listings for specific keywords by polling search_lots with status=active and checking listed_at timestamps
  • Build a lot-watching dashboard that alerts when status changes from active to ended on tracked lot_id values
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Clean Sweep Auctions have an official developer API?+
Clean Sweep Auctions does not publish an official public developer API or developer documentation as of the time of writing.
What does `search_lots` return for completed auctions, and how is that different from active lots?+
When status is set to completed, search_lots searches the recently closed auction pool and returns the same row shape — lot_id, title, url, listing_type, and status metadata — as active searches. The get_lot call on a completed lot will show status: ended, a null next_bid (since bidding is closed), and a bid_count reflecting final bid activity. Active lots return a live next_bid amount as long as the auction is open.
Does the API return seller information or buyer details for lots?+
Not currently. The API covers lot identity, pricing economics (next_bid, bid_count), grading fields, listing timestamps, and status. Seller profiles and buyer details are not part of the response shape. You can fork this API on Parse and revise it to add a seller-detail endpoint if that data is accessible on the lot page.
Can I search across all three listing pools in a single API call?+
No — each search_lots call targets exactly one pool (active, completed, or fixed_price). Covering all three requires three separate requests. You can fork this API on Parse and revise it to add a combined endpoint that fans out and merges results from all pools.
Are bid history or individual bidder records available through `get_lot`?+
Not currently. get_lot returns the aggregate bid_count and the current next_bid amount, but individual bid records and bidder identities are not included. You can fork this API on Parse and revise it to add a bid-history endpoint if that data is exposed on the lot's detail page.
Page content last updated . Spec covers 2 endpoints from marketplace.cleansweepauctions.com.
Related APIs in MarketplaceSee all →
lelands.com API
Access data from lelands.com.
siriussportsauctions.com API
Search current and past Sirius Sports Cards auction lots and fixed-price items by your criteria, then view detailed information about specific cards including current auction prices and historical prices realized. Browse anonymously to discover cards and compare pricing across live auctions and completed sales without needing an account.
wheatlandauctionservices.com API
Search through Wheatland Auction Services' current sports card and memorabilia auction by keywords or categories to find lots that interest you, then view detailed information about individual items including pricing data. Browse anonymously without needing an account to discover and compare available lots before bidding.
collectauctions.com API
Search through Collect Auctions lots and view detailed information about each item, including current status (sold, unsold, or active), opening bid, final sale price with premium included, bid count, and auction dates. Access gallery views of lots and get comprehensive details to research auction history and track specific items.
bid.memorylaneinc.com API
Access data from bid.memorylaneinc.com.
milehighcardco.com API
Search Mile High Card Company's current auction catalog by keyword and view detailed pricing information for individual lots, including separate price roles and completion status independent of scheduled auction timing. Perfect for tracking specific cards and monitoring auction activity without needing to browse the website directly.
catalogs.scpauctions.com API
Access data from catalogs.scpauctions.com.
rrauction.com API
Search and browse current and past auction lots from RR Auction, including detailed information about each item's description, estimated value, and bidding history. Find specific items of interest by searching across their complete catalog of collectibles, memorabilia, and rare goods.