COMC search API

Endpoint facts

Method

GET

API path

/comc/search

Auth

apiKey

Credits

4 credits/request

Platform

COMC

Response schema

#/definitions/comc.searchResponseDoc

Overview

Searches or browses COMC's (comc.com) live consignment marketplace for graded and ungraded trading cards. Each result row is a distinct card+grade combination (COMC's own category/search grid aggregates every seller's copy under one row); chain a row's handle into the listing endpoint for the per-seller breakdown. At least one of category or query is typically useful, but both are optional -- omitting both searches all categories. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

4 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- `category` must be one of `comc-categories`' returned slugs; an unknown value returns `400` before any upstream request is made. Same for `sort`, each value in `attributes`, `condition`, and `page_size`. - Two facets visible on comc.com's own category/search page -- Listing Format (Auction/Buy Now/Both) and Sold Out (Ignore/Include/Only Sold Out) -- are **not** exposed as request filters here. Both are wired to an ASP.NET `__doPostBack` control on comc.com's own site rather than a plain URL parameter (confirmed live), so a stateless GET request cannot drive them the way `sort`/`attributes`/`condition` are driven. - `set_description` is COMC's own descriptive text for the set/base/parallel combination as a single string (e.g. `"Topps Chrome - [Base] - Red Wave Refractor"`) -- deliberately not further split into separate set/base/ parallel fields, since set names themselves routinely contain dashes and brackets, making that split unreliable to do generically. - `grade_label` and `print_run` are only present for graded cards (e.g. `"PSA 10 GEM MT"` / `"#/5"`); both are omitted for ungraded cards. - `price` is the price COMC's own search/category grid displays for this row. Best-effort labeled: COMC's grid shows one price per card+grade row aggregating potentially several sellers' listings, and this has not been live-confirmed to always be the lowest current listing -- treat it as COMC's own representative price for the row, not a guaranteed minimum. - A search with no matching cards returns `200` with an empty `cards` array. Example response: ```json { "code": 200, "msg": "OK", "data": { "category": "Baseball", "page": 1, "total_count": 2653613, "cards": [ { "handle": "Cards/Baseball/2021/Topps_Chrome_-_Base_-_Red_Wave_Refractor/84/Nolan_Arenado/17500366/Graded/PSA/10", "url": "https://www.comc.com/Cards/Baseball/2021/Topps_Chrome_-_Base_-_Red_Wave_Refractor/84/Nolan_Arenado/17500366/Graded/PSA/10", "year": "2021", "set_description": "Topps Chrome - [Base] - Red Wave Refractor", "card_number": "84", "subject": "Nolan Arenado", "grade_label": "PSA 10 GEM MT", "print_run": "#/5", "image_url": "https://img.comc.com/i/Baseball/2021/Topps-Chrome---Base---Red-Wave-Refractor/84/Nolan-Arenado.jpg", "price": 64930.00 } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related