Fanatics Collect Auction Lots Scraper

Extract public Fanatics Collect auction lots from the weekly marketplace as structured snapshots. Get listing and auction IDs, lot numbers, titles, displayed current bids, currency, bid counts, scheduled auction dates and images without logging in.

For collectible dealers, card-market analysts and spreadsheet users who need repeatable weekly inventory and valuation inputs. This Actor reads public cards; it never bids, buys or accesses an account.

Who is it for?

Collectible dealers refresh weekly auction inventory; analysts compare displayed bid snapshots; spreadsheet users review lots without manual copying.

Why use this Actor?

• Join snapshots by listing UUID instead of matching changing titles.
• Keep displayed bids separate from final-sale prices.
• Preserve auction identity and lot-number suffixes.
• Export clean rows to JSON, CSV, Excel or your own data pipeline through Apify datasets.
• Stop at your chosen global lot/page limits without charging duplicate lots.

What can I scrape?

The public weekly auction marketplace at https://www.fanaticscollect.com/marketplace?type=WEEKLY.

The current marketplace determines which auctions and lots appear. No fixed auction number is hardcoded. The Actor follows consecutive search pages, currently observed at 48 lots per page, with a maximum page index of 50. This is a bounded marketplace snapshot, not a complete historical archive.

Premier auctions, Buy Now, sold history, individual detail descriptions, certification enrichment, watchlists, bidding and alerts are not supported. Do not infer those capabilities from the general Fanatics Collect brand.

Getting started

1. Open this Actor in Apify Console.
2. Keep the weekly marketplace URL or add a supported starting page.
3. Set maxItems and maxPages.
4. Start the Actor and inspect its default dataset.
5. Export the rows or connect the dataset to your downstream workflow.

{
  "startUrl": "https://www.fanaticscollect.com/marketplace?type=WEEKLY",
  "maxItems": 100,
  "maxPages": 3
}

Input parameters

Field	Default	Meaning
startUrl	Weekly marketplace, page 1	HTTPS www.fanaticscollect.com marketplace URL with type=WEEKLY and optional page=1–50
maxItems	100	Global maximum unique weekly lots saved, 1–2400
maxPages	3	Consecutive pages visited, 1–50; starting page plus this limit cannot exceed page 50

Only type and page URL parameters are accepted. Other filters and unsupported URL routes fail validation rather than being silently ignored. Zero/unlimited limits are not supported. No user account or proxy credential is required; no proxy fallback is enabled.

Pagination and coverage

Collection stops at the first of the lot limit, page limit or visible last page. The upstream search can cap results, and its page size/order can change. Lots appearing on multiple pages are deduplicated by listing ID within each run. Separate runs intentionally return new snapshots of the same lots.

Large 50-page runs can take substantially longer in the cloud than locally. The default platform timeout is one hour; lower user timeouts may leave a failed partial snapshot. Billing limits can stop delivery earlier.

Changing bids and inventory during collection can shift search order. This Actor does not promise an atomic snapshot or exhaustive coverage of all source inventory.

Output fields

Field	Meaning
listingId	Public listing UUID used for joins
auctionId, auctionName	Weekly auction identity
lotNumber	Source lot number including suffixes; null when the source omits it
title	Displayed card title
subtitle	Displayed grading/population text, or null
url	Canonical public weekly lot URL
currentBid, currency	Current displayed bid in currency units
bidCount	Displayed number of bids
auctionStatus, listingStatus	Source auction/listing status
auctionStartsAt, auctionEndsAt	Scheduled auction timing in UTC
images	Public source image URLs, not downloaded files
scrapedAt	UTC observation timestamp

The default dataset contains one row per unique listing. A SUMMARY key-value record contains saved count and configured limits.

Output example

This excerpt reflects an observed weekly card; volatile bid values are illustrative of that snapshot, not current quotes.

{
  "listingId": "9fe1b4d0-b8d9-11f1-9aff-0a58a9feac02",
  "auctionName": "Weekly Auction #247",
  "lotNumber": "4515",
  "title": "2003 Exquisite Collection Number Piece Magic Johnson PATCH AUTO /32 #NP-MA PSA 7 NRMT",
  "currentBid": 74,
  "currency": "USD",
  "bidCount": 11,
  "auctionEndsAt": "2026-10-12T02:00:00Z"
}

The actual row also includes the fields documented above. A displayed current bid is not a hammer price, valuation recommendation or completed sale.

How much does it cost to extract Fanatics Collect auction lots?

Pay per event: a one-time $0.005 start fee, plus a tier-dependent charge for each unique saved lot. The BRONZE rate is $0.0028 per lot; consult the Actor's live Pricing tab for the active tier prices.

At that BRONZE rate, 10 lots cost $0.033, 100 cost $0.285 and 1,000 cost $2.805. Start is charged once after input validation. Duplicate or rejected lots have no item charge. A failed run can still incur its start fee and charges for already saved partial rows. Your maximum charge/run settings can also limit delivery.

Timing and limitations

auctionEndsAt is the scheduled close / beginning of extended bidding from the public auction metadata. It is not a guarantee of the final bidding deadline for an individual lot. Use the source website for bidding decisions.

No item detail page is visited. Images remain external URLs and may change or expire. Population text is copied as displayed, not independently verified. This Actor is not affiliated with Fanatics Collect.

Failure behavior and troubleshooting

Malformed inputs fail before work begins. Transient navigation/data failures receive at most one retry with a fresh anonymous browser context. Missing required fields, challenge pages, empty response shells or repeated pagination fail explicitly instead of claiming a successful empty snapshot.

If the source changes, retry later only after inspecting the error. Do not treat partial rows from a failed run as a complete result. An empty weekly marketplace is not currently a supported successful no-result mode.

Integrations

• Google Sheets / Excel: export rows for lot review and inventory planning.
• Database: append snapshots keyed by listing ID and observation timestamp; compare bids across scheduled runs.
• Apify schedules: run periodic snapshots yourself; compare and alert in your own workflow. The Actor does not send alerts.
• Webhooks: trigger your pipeline after a successful run and read the default dataset.

API usage

Use your own Apify token securely. The synchronous dataset endpoint returns rows after completion; for long jobs use asynchronous runs and follow the same run ID.

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~fanatics-collect-auction-lots-scraper/run-sync-get-dataset-items' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"maxItems":100,"maxPages":3}'

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/fanatics-collect-auction-lots-scraper').call({ maxItems: 100, maxPages: 3 });
const { items } = await client.dataset(run.defaultDatasetId).listItems({ limit: 100 });

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/fanatics-collect-auction-lots-scraper').call(run_input={'maxItems': 100, 'maxPages': 3})
items = client.dataset(run['defaultDatasetId']).list_items(limit=100).items

MCP usage

Select a stable Actor subset:

claude mcp add --transport http apify \
  'https://mcp.apify.com?tools=automation-lab/fanatics-collect-auction-lots-scraper'

{"mcpServers":{"apify":{"type":"http","url":"https://mcp.apify.com?tools=automation-lab/fanatics-collect-auction-lots-scraper"}}}

Use that HTTP configuration in Claude Desktop, Cursor or VS Code with an MCP-capable client. Example prompt: “Extract 10 weekly auction lots, then show title, currentBid and bidCount.”

Discover actual tool names and schemas with scoped tools/list. Selection also adds run/data helper tools; discovery is not permission to execute. An example authorized request is “Collect 100 public weekly lots and show their titles and bids.”

Start once, retain the returned run ID and storage IDs. If pending, check that same run with bounded backoff (2, 4, 8 seconds capped at 10) and a total deadline such as 120 seconds. Configure the client timeout above the selected server wait plus transport margin. A timeout is not a reason to start a duplicate run. At deadline report pending with its ID; report terminal failures honestly.

After success, read bounded dataset pages of 20 source rows, at most 100 rows and 64 KiB of serialized UTF-8 content admitted to model context, whichever comes first. Enforce bytes host-side; omit/summarize oversized rows with disclosure. Track source offsets, report partial/truncated results and keep full exports outside model context. Clients without host-side interception cannot guarantee that byte ceiling. No numeric token-saving claim is made.

Legality and diagnostics

Use public data responsibly, comply with applicable terms and laws, and avoid excessive request frequency. Do not use this dataset as an authoritative bidding or investment feed.

Failed operations send sanitized diagnostic input, exceptions and Actor/build/run IDs to our private GlitchTip service for repair. Secret fields and URL queries are removed; reports are retained for 30 days. No login or private buyer data is collected by this Actor. No AI service is used at runtime. Browser sessions are ephemeral and closed after each page; datasets, summaries and platform logs follow your Apify storage retention and deletion settings. Delete run storage through Apify when no longer needed. For assistance use the Actor's Apify Issues tab.

FAQ

Does it return sold prices or Premier lots? No. This release is limited to public weekly marketplace cards.

Can I filter by player or grade? Not in this release. Unsupported URL filters are rejected. Filter exported snapshots in your own tools.

Can I schedule it? Yes, using Apify schedules. Comparison and alerts belong in your downstream system.

Why did it return fewer than maxItems? The page limit, visible last page, source coverage or billing limit can stop collection earlier.

Why did it fail with zero rows? The source may have challenged the browser or changed its public response shape. The Actor fails rather than silently delivering an empty inventory.

Related Actors

For a separate auction-market workflow, see Bring a Trailer Auctions & Results Scraper. It covers vehicle auctions, not Fanatics Collect cards.