COMC card listing detail API

Endpoint facts

Method

GET

API path

/comc/listing

Auth

apiKey

Credits

4 credits/request

Platform

COMC

Response schema

#/definitions/comc.listingResponseDoc

Overview

Returns one card+grade combination's full detail from COMC (comc.com): card identity and every seller's individual for-sale copy (owner, item id, price). handle is the value returned by comc_search's CardSummary.handle field (or the equivalent comc.com card URL path). 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

Response behavior

- A `handle` that is empty, or does not start with `Cards/` (after stripping a leading slash or a `https://www.comc.com` prefix), returns `400` before any upstream request is made. - `set_description`, `grade_label`, `year`, and `card_number` are parsed from the page's own `<title>` tag, which reliably carries the full card identity in one place (e.g. the title `"2021 Panini Absolute - [Base] - Red #36 - Josh Allen"` yields `year: "2021"`, `set_description: "Panini Absolute - [Base] - Red"`, `card_number: "36"`, `subject: "Josh Allen"`). `grade_label` is only present for graded cards. - `listings` is every individual seller copy of this exact card+grade combination, each with its own numeric `item_id`, `owner` username, `owner_url`, and `price` -- not a single aggregate price the way `comc-search`'s row-level `price` is. - `parallels` is every sibling parallel of the same base card (e.g. `"[Base]"`, `"Blue"`, `"Green"`), from the card's own "Parallels & Grades" table, each with COMC's own displayed price, a `handle` for a follow-up `comc-listing` lookup, and `for_sale_count`. A parallel with no current listings has `sold_out: true` and `price: 0` (COMC itself displays `$0.00` for that row rather than omitting it). - A `handle` COMC no longer serves returns `404`. Example response: ```json { "code": 200, "msg": "OK", "data": { "handle": "Cards/Football/2021/Panini_Absolute_-_Base_-_Red/36/Josh_Allen/17779360", "year": "2021", "set_description": "Panini Absolute - [Base] - Red", "card_number": "36", "subject": "Josh Allen", "image_url": "https://img.comc.com/i/Football/2021/Panini-Absolute---Base---Red/36/Josh-Allen.jpg", "total_listings": 2, "parallels": [ { "name": "[Base]", "handle": "Cards/Football/2021/Panini_Absolute_-_Base/36/Josh_Allen/17777799", "price": 1.29, "for_sale_count": 34 }, { "name": "Orange", "handle": "Cards/Football/2021/Panini_Absolute_-_Base_-_Orange/36/Josh_Allen/17778525", "sold_out": true } ], "listings": [ { "item_id": 156183522, "owner": "Severin", "owner_url": "https://www.comc.com/Users/Severin", "price": 1.04 }, { "item_id": 156183600, "owner": "crossroad", "owner_url": "https://www.comc.com/Users/crossroad", "price": 2.15 } ] } } ```

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