Autographed memorabilia catalog monitoring
Use Pristine Marketplace endpoints to turn autographed memorabilia catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Pristine Marketplace's public Shopify storefront into structured retail data for authenticated, hand-signed sports and pop-culture memorabilia -- full product catalog and detail, collection and sport-specific navigation, storefront pages, a store-wide review feed, and sitemap discovery, all pinned to Pristine Marketplace's own storefront URL so no url parameter is needed. Credential-free.
Get Pristine Marketplace products, collections, pages, and store reviews as structured JSON through a pinned endpoint family — no url parameter needed.
Endpoint families
6
Documented params
36
Examples
13
Live catalog snapshot
Active endpoints
13
Methods
GET
Required params
19
Schema refs
13
{
"platform": "Pristine Marketplace",
"endpoint": "pristine-marketplace-store",
"method": "GET",
"path": "/pristine-marketplace/store",
"auth": "apiKey"
}Use cases
Get Pristine Marketplace products, collections, pages, and store reviews as structured JSON through a pinned endpoint family — no url parameter needed.
Use Pristine Marketplace endpoints to turn autographed memorabilia catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Use Pristine Marketplace endpoints to turn sport-specific collection and navigation research into repeatable API requests with documented inputs and JSON responses.
Use Pristine Marketplace endpoints to turn store review and sitemap discovery into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Pristine Marketplace endpoint catalog — 13 endpoints, 36 documented request parameters, and 13 published response schemas — the same catalog Docs and Playground run against.
13 documented Pristine Marketplace endpoints, grouped into 8 request families — Products, Collections and Pages, plus 5 more.
36 request parameters are documented across those Pristine Marketplace endpoints, 19 of them required — the full input contract is public before you write any integration code.
13 of the 13 Pristine Marketplace endpoints ship a recorded example response, and 13 carry a documented response schema — you can code against the real JSON before the first request.
Pristine Marketplace endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
13 hosted MCP tools back the Pristine Marketplace endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/pristine-marketplace/products
/pristine-marketplace/collections
/pristine-marketplace/pages
/pristine-marketplace/search
/pristine-marketplace/reviews
/pristine-marketplace/sitemap/urls
Featured endpoints
/pristine-marketplace/storeReturns normalized storefront metadata for Pristine Marketplace (https://www.pristinemarketplace.com), sourced from credential-free storefront JSON. This endpoint is a brand-pinned wrapper around the generic Shopify store family: the storefront URL is fixed server-side, so no `url` parameter is accepted. If the vanity domain blocks `/products.json`, the service may fall back to a public `*.myshopify.com` domain discovered from the storefront page, or to the storefront's own embedded page data for storefronts that expose neither.
Response notes
- Returns the resolved source URL used for JSON requests. - Includes `myshopify_domain`, store name, currency, country, and published product/collection counts when `/meta.json` exposes them. - Blocked pages, malformed JSON, missing Shopify roots, and unavailable fallback domains return upstream errors. - If the classic `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the storefront's own pages directly and parsing their embedded structured data. When this fallback was used, `transport_mode` is `ssr_embedded`; it is omitted entirely for stores served by the classic catalog JSON. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "requested_url": "https://www.pristinemarketplace.com", "source_url": "https://www.pristinemarketplace.com", "domain": "www.pristinemarketplace.com", "source_domain": "www.pristinemarketplace.com", "name": "Pristine Marketplace", "currency": "USD", "country": "US", "published_products_count": 12000 } } ```
MCP tool pristine_marketplace_store
/pristine-marketplace/productsReturns normalized products from Pristine Marketplace's (https://www.pristinemarketplace.com) public product catalog. The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty products array.
Response notes
- Valid empty result pages return `200` with an empty `products` array. - Product prices are normalized to decimal currency units. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - If the classic `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to the storefront's own conventional "all products" collection page and parses its embedded search-result payload. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, `total_items`, and `total_pages`, plus additive per-product fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`). `limit` is honored as an upper bound; the underlying page size is fixed by the storefront and cannot be requested larger in fallback mode. All of the above are omitted entirely for stores served by the classic catalog JSON. - When the `ssr_embedded` fallback was used, the response may also include `facets` and `facets_stats`, mirroring the storefront's own filter sidebar for that listing. - This brand-pinned endpoint does not accept `sortBy` or facet-filter query parameters (out of scope -- use the generic `/shopify/products` endpoint with `url` set to this brand's storefront for sort/filter support). The response reuses the same shared DTO as the generic family, which carries `sort`/`filters` fields for that feature; they are always omitted here since this endpoint never populates them. `sort` allowed values (never actually returned by this endpoint, listed for schema completeness): `sortLTH`, `sortHTL`, `newest`. This brand-pinned endpoint also does not accept the generic family's `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`option_*` Storefront Filtering params (same out-of-scope reasoning -- use the generic `/shopify/products` endpoint with `url` set to this brand's storefront). The response DTO carries the matching `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`variant_options` fields for that feature; they are always omitted here since this endpoint never populates them. `sort_by` allowed values (never actually returned by this endpoint, listed for schema completeness): `manual`, `best-selling`, `title-ascending`, `title-descending`, `price-ascending`, `price-descending`, `created-ascending`, `created-descending`. `transport_mode` allowed values: `ssr_embedded`, `storefront_filtered` (only ever these two values; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.pristinemarketplace.com", "source_url": "https://www.pristinemarketplace.com", "page": 1, "limit": 2, "products": [ { "id": "8463815540780", "handle": "washington-commanders-sts22-f-s-authentic-football-helmet", "title": "Washington Commanders STS22 F/S Authentic Football Helmet", "url": "https://www.pristinemarketplace.com/products/washington-commanders-sts22-f-s-authentic-football-helmet", "price": 509, "available": true } ] } } ```
MCP tool pristine_marketplace_products
/pristine-marketplace/products/{handle}Returns normalized product detail for one Pristine Marketplace (https://www.pristinemarketplace.com) product handle. The storefront URL is fixed server-side; `handle` is the product's URL slug.
Response notes
- Product prices from `.js` responses are normalized from cent values to decimal currency units. - Missing product handles return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing product fields return upstream errors. - If the classic product `.js` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the product detail page directly and parsing its embedded structured data (a richer Next.js data block when the storefront exposes one, otherwise the page's schema.org JSON-LD `ProductGroup`/`Product` block). When this fallback was used, the response includes `transport_mode: "ssr_embedded"` and additive fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`). `transport_mode` is omitted entirely for stores served by the classic transport. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.pristinemarketplace.com", "source_url": "https://www.pristinemarketplace.com", "product": { "id": "8463815540780", "handle": "washington-commanders-sts22-f-s-authentic-football-helmet", "title": "Washington Commanders STS22 F/S Authentic Football Helmet", "price": 509, "images": [{"url": "https://cdn.shopify.com/s/files/1/0553/6196/2028/files/12503c93-75b7-4671-90c8-a873cb8c6e8e.png"}] } } } ```
MCP tool pristine_marketplace_product
/pristine-marketplace/products/{handle}/recommendationsReturns normalized recommended products for one Pristine Marketplace (https://www.pristinemarketplace.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side.
Response notes
- Missing product handles return `404` when Shopify returns not found while resolving the seed product. - Valid empty recommendation arrays return `200` with an empty `products` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic recommendations endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the seed product's own detail page (recommendations are embedded there). When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, with the same additive product fields documented for the products endpoint. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.pristinemarketplace.com", "source_url": "https://www.pristinemarketplace.com", "handle": "washington-commanders-sts22-f-s-authentic-football-helmet", "product_id": "8463815540780", "intent": "related", "limit": 10, "products": [{"handle": "example-related-product", "title": "Example Related Product"}] } } ```
MCP tool pristine_marketplace_product_recommendations
/pristine-marketplace/collectionsReturns normalized collections from Pristine Marketplace (https://www.pristinemarketplace.com). The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty collections array.
Response notes
- Valid empty result pages return `200` with an empty `collections` array. - Blocked pages, malformed JSON, and missing `collections` roots return upstream errors. - The storefront maintains hundreds of narrow per-player/per-team/per-item-type collections (e.g. `aaron-judge`, `aaron-judge-jerseys`, `pop-culture`) rather than a small set of broad category collections; not every such collection has products in stock at a given time. - If the classic `/collections.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to enumerating collections from the storefront's own `collections` sitemap. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, and `title` is a best-effort derivation from the handle -- **not** the storefront's real display name. `products_count` and other classic-only fields are omitted, never fabricated. - In fallback mode, `handle` is derived from the last path segment of the collection URL and is not guaranteed unique across nested sub-collections; use the item's own `url` to identify a specific one. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.pristinemarketplace.com", "source_url": "https://www.pristinemarketplace.com", "page": 1, "limit": 2, "collections": [ { "id": "278435758160", "handle": "pop-culture", "title": "Pop Culture Memorabilia", "url": "https://www.pristinemarketplace.com/collections/pop-culture", "products_count": 24 } ] } } ```
MCP tool pristine_marketplace_collections
/pristine-marketplace/collections/{handle}/productsReturns normalized products from one Pristine Marketplace (https://www.pristinemarketplace.com) collection. The storefront URL is fixed server-side; `handle` is the collection's URL slug (typically a player, team, or memorabilia-type collection, e.g. `pop-culture`).
Response notes
- Valid empty result pages return `200` with an empty `products` array -- many of the storefront's narrow per-player/per-team collections are momentarily out of stock rather than nonexistent; a `200` with an empty array is not itself evidence the handle is wrong. - Missing collections return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - If the classic collection `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the collection listing page directly and parsing its embedded search-result payload. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, `total_items`, `total_pages`, plus additive per-product fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`) and may include `facets`/`facets_stats`. `limit` is honored as an upper bound only; underlying page size is fixed by the storefront in fallback mode. - This brand-pinned endpoint does not accept `sortBy` or facet-filter query parameters (out of scope -- use the generic `/shopify/collections/{handle}/products` endpoint with `url` set to this brand's storefront for sort/filter support). The response reuses the same shared DTO as the generic family, which carries `sort`/`filters` fields for that feature; they are always omitted here since this endpoint never populates them. `sort` allowed values (never actually returned by this endpoint, listed for schema completeness): `sortLTH`, `sortHTL`, `newest`. This brand-pinned endpoint also does not accept the generic family's `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`option_*` Storefront Filtering params (same out-of-scope reasoning -- use the generic `/shopify/collections/{handle}/products` endpoint with `url` set to this brand's storefront). The response DTO carries the matching `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`variant_options` fields for that feature; they are always omitted here since this endpoint never populates them. `sort_by` allowed values (never actually returned by this endpoint, listed for schema completeness): `manual`, `best-selling`, `title-ascending`, `title-descending`, `price-ascending`, `price-descending`, `created-ascending`, `created-descending`. `transport_mode` allowed values: `ssr_embedded`, `storefront_filtered` (only ever these two values; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.pristinemarketplace.com", "source_url": "https://www.pristinemarketplace.com", "collection": "pop-culture", "page": 1, "limit": 2, "products": [ {"handle": "billie-eilish-authentic-signed-framed-hit-me-hard-and-soft-album-flat-bas", "title": "Billie Eilish Authentic Signed & Framed Hit Me Hard and Soft Album Flat BAS", "price": 709} ] } } ```
MCP tool pristine_marketplace_collection_products
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape Pristine Marketplace
Crawlora's Pristine Marketplace endpoints return product, collection, page, review, search, and sitemap data as normalized JSON with one API key -- Pristine Marketplace's storefront URL is pinned server-side, so no account or url parameter is required.
Call /pristine-marketplace/products for the full public product catalog with pagination, or /pristine-marketplace/collections and /pristine-marketplace/collections/{handle}/products to browse by player, team, or memorabilia-type collection.
Pass a product handle (from a /pristine-marketplace/products or collection result) to /pristine-marketplace/products/{handle} for full detail, or to /pristine-marketplace/products/{handle}/recommendations for related products.
Send a query to /pristine-marketplace/search for full-text results, or to /pristine-marketplace/search/suggest for predictive product, collection, and query suggestions.
Call /pristine-marketplace/reviews for the storefront's public Judge.me review feed, or /pristine-marketplace/pages and /pristine-marketplace/pages/{handle} for static pages including its "Shop by Sport" navigation landing pages (NFL, MLB, NBA, NHL, NASCAR).
FAQ
/pristine-marketplace/* pins Pristine Marketplace's own storefront URL (https://www.pristinemarketplace.com) server-side, so every call needs only your Crawlora API key -- no url parameter.
No -- only your Crawlora API key. Pristine Marketplace's storefront data is collected from its public, credential-free storefront surface.
Yes -- /pristine-marketplace/reviews returns one page of the storefront's public Judge.me review feed, the same most-recent-first feed the storefront's own on-page review widget draws from.
To /pristine-marketplace/pages -- its NFL, MLB, NBA, NHL, and NASCAR navigation entries resolve to static page handles there, not to a separate category endpoint.