Skip to documentation
Developers
DOCUMENTATIONOverview
CARDCOUNTER POS / DEVELOPERS

Build with
the card market.

Identify exact printings, read market prices and history, inspect live listings, and bring that context into your own software. Everything starts with a clear, versioned API.

Start building Browse API reference
JSON over HTTPS Account API keys Versioned v1
Your first market requestv1
curl --request GET \  --url 'https://pokepos-market-api.vercel.app/v1/identify?q=Mew%20ex%2066&set=30th%20Celebration' \  --header 'Authorization: Bearer YOUR_API_KEY'
Response illustrative JSON
{  "source": "tcgplayer-public-site",  "query": "Mew ex 66",  "parsed": {    "name": "Mew ex",    "cardNumber": "66",    "setHint": "30th Celebration"  },  "matchedSet": {    "name": "30th Celebration",    "slug": "30th-celebration",    "count": 100  },  "searchedCount": 18,  "totalSearchResults": 18,  "truncated": false,  "candidates": [    {      "productId": 716465,      "name": "Mew ex - 066/128",      "cardNumber": "066/128",      "matchScore": 440    }  ]}
Example values can change with the source.
01 / THE PLATFORM

Choose how to use market data.

Two products use the same market foundation. Pick the one that fits where you work.

PRODUCT 01 · FOR BUILDERS

Market Data API

Direct JSON access for your app or service. Resolve product identity, read condition-level prices, retrieve history, and page through listings.

Explore the API
PRODUCT 02 · FOR CARDCOUNTER POS SHOPS

Market Pricing Add-on

Bring market observations into the CardCounter POS Stockroom beside your own SKU price. Staff confirm the printing and decide what to save.

See the add-on
02 / GET STARTED

From a card name to a useful price.

The shortest path is to resolve the printing, then ask for the market section you need.

01

Get an API key

Choose an access tier and send your bearer key from your server.

02

Find the printing

Match a name and collector number, with a set hint when needed.

03

Read the market

Use one snapshot or select a focused price, history, or listings route.

03 / EXPLORE THE API

Find the right endpoint.

All 14 endpoints

Identify exact cards

Turn a name, number, or photo into ranked printings before using a price.

Card identity

Read market signals

Inspect SKU prices, sales history, and current seller offers with source timing.

Market prices

Bring the image

Retrieve a verified image URL alongside product details and attributes.

Card images
Prefer the machine-readable contract?OpenAPI 3.1 contains the complete request and response schemas.
View OpenAPI
READY WHEN YOU ARE

Make your first call.

Start with the quickstart, then browse every route and response field in the reference.

Read the quickstart