Cardova APIcardova.co.jp ↗
Access Cardova Japan trading-card auction data: series listings, lot details, bid counts, JPY/USD prices, grading info, and filtered search across live and past auctions.
What is the Cardova API?
The Cardova API exposes 4 endpoints covering auction series metadata and individual lot data from cardova.co.jp, Japan's trading-card auction platform. Starting with list_auction_series, you can enumerate live, closed, or suspended series by their codes (e.g. A207), then drill into per-lot data including current bid in JPY and USD, bid counts, grading company and grade, population counts, card language, and scheduled end dates.
curl -X GET 'https://api.parse.bot/scraper/409647a2-eb21-422b-ab7e-b6c70200b77e/list_auction_series?status=live' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the auction series (e.g. A207) currently in the requested state: live (open for bidding, typically 1-3 series), close (all past series, newest first; several hundred entries) or suspended (usually empty). Each entry carries the series code and its id plus publish-start and scheduled-end timestamps (JST, ISO 8601). One request; no pagination. The series code is the input to list_series_lots.
| Param | Type | Description |
|---|---|---|
| status | string | Which auction state to list. |
{
"type": "object",
"fields": {
"count": "integer number of series returned",
"series": "array of series entries: series (code such as A207), series_id, status, publish_start_date, scheduled_end_date (ISO 8601 with +09:00 offset)",
"status": "the requested state echoed back"
},
"sample": {
"data": {
"count": 1,
"series": [
{
"series": "A207",
"status": "live",
"series_id": "01M09D6A257N7ADHKVM6G4WSG2",
"publish_start_date": "2026-08-27T12:00:00+09:00",
"scheduled_end_date": "2026-09-06T21:00:00+09:00"
}
],
"status": "live"
},
"status": "success"
}
}About the Cardova API
Auction Series and Lot Data
The list_auction_series endpoint accepts a status parameter (live, close, or suspended) and returns each series' code, its series_id, publish_start_date, and scheduled_end_date in ISO 8601 with a +09:00 offset. Live status typically returns one to three open series; close returns several hundred past series ordered newest-first. The list_series_lots endpoint takes a series code from that list and returns a paged set of lots — up to 96 per page via the limit parameter — along with fields such as lot, lot_number, title, year, brand, set_name, player, card_number, language, grading_company, grade, current_bid_jpy, current_bid_usd, bid_count, and population counts. The usd_rate field shows the JPY-per-USD exchange rate the site publishes, used to derive all USD values.
Latest Auction and Search
The get_latest_auction endpoint needs no input. It identifies the most recent series (the live series with the newest publish_start_date, falling back to the newest closed series) and fetches every lot in one call, returning the full lot array alongside complete (true when all pages were retrieved), failed_pages (listing any pages that could not be fetched), and the series' publish_start_date. This is useful for building snapshots or seeding a database without managing pagination manually.
The search_auction_lots endpoint maps to the site's filter panel and supports status (live or close), kind (tcg for the weekly TCG auction or sports for Sports & Others), keyword for free-text search, grades as comma-separated grade bucket codes (e.g. 10, 9.5, auth), series to restrict results to specific series codes, sort, page, and limit. Results share the same lot-level field shape as the other endpoints. has_more signals whether additional pages exist, and total gives the full match count for the applied filters.
The Cardova API is a managed, monitored endpoint for cardova.co.jp — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when cardova.co.jp changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official cardova.co.jp API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor current bid prices in JPY and USD for graded cards across all live Cardova auction series.
- Build a price history database by iterating
closeseries vialist_auction_seriesand fetching lots withlist_series_lots. - Alert users when a keyword-matched card (e.g. a specific player or character) appears in a live auction using
search_auction_lots. - Compare population counts across grading companies for the same card to evaluate relative scarcity.
- Snapshot an entire active auction at once using
get_latest_auctionto track bid movement over time. - Filter lots by grade bucket (e.g. only PSA 10 or BGS 9.5) and language to narrow searches for specific collector targets.
- Track bid counts on specific lots across polling intervals to identify auctions with sudden bidding activity.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Cardova offer an official developer API?+
What does `search_auction_lots` return, and how does filtering work?+
status (live or close), kind (tcg or sports), keyword, grades (comma-separated bucket codes like 10, 9.5, auth), and optionally one or more series codes. Each lot in the response includes title, current_bid_jpy, current_bid_usd, bid_count, grading_company, grade, language, and scheduled_end_date, among other fields. The total field tells you how many lots match across all pages.What does `get_latest_auction` do when multiple series are live simultaneously?+
publish_start_date. If no series is currently live, it falls back to the most recently closed series. The response includes complete (true when every lot was retrieved) and failed_pages (an array of page numbers that could not be fetched), so you can tell whether the result set is partial.Does the API expose seller information, buyer identities, or final hammer prices after auction close?+
Is pagination automatic, or do I need to manage it myself?+
list_series_lots and search_auction_lots are manually paged: you supply page and limit (capped at 96), and the has_more field tells you whether another page exists. get_latest_auction handles pagination internally and returns all lots in a single response, but only for the most recent series. For older series you manage pagination yourself via list_series_lots.