Hobbiesville APIhobbiesville.com ↗
Access Hobbiesville's full Pokémon single-card catalogue: set lists, rarity/finish filters, per-condition stock, sell prices, buylist offers, and live pricing models.
What is the Hobbiesville API?
The Hobbiesville API exposes 8 endpoints covering the store's complete Pokémon singles catalogue across English and Japanese lines. The search_cards endpoint returns per-condition stock status, sell price in CAD, market price, and buylist cash/credit offers for every matching card whether in stock or sold out. Companion endpoints supply the set, rarity, and finish vocabularies needed to filter searches precisely, while get_pricing_model and get_set_pricing_formulas derive live regression formulas from current listings.
curl -X GET 'https://api.parse.bot/scraper/d4b0f843-b968-444f-a669-9a8aeca50a72/list_sets?query=Paldean' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the complete list of set names the store's Pokémon catalogue is organised by for one language line, in the same order as the site's Set filter (newest sets first). Each entry carries a display name and the exact code to pass as set_name to search_cards (currently identical strings). One round trip; the list is small (a few hundred entries) and never paginated. An optional free-text query narrows the list to sets whose name contains it (case-insensitive substring); an empty result for a query that matches nothing is a valid empty list. language selects the English line (default) or the Japanese line; set codes are only valid for searches in the same language.
| Param | Type | Description |
|---|---|---|
| query | string | Optional substring to match against set names (case-insensitive). Omitted = all sets. |
| language | string | Catalogue line to list sets for. |
{
"type": "object",
"fields": {
"sets": "array of {name, code}; code is the value accepted by search_cards.set_name",
"query": "the query filter that was applied (empty string when none)",
"total": "integer count of sets returned",
"language": "the language line the list belongs to"
},
"sample": {
"data": {
"sets": [
{
"code": "SV4a: Shiny Treasure ex",
"name": "SV4a: Shiny Treasure ex"
}
],
"query": "SV4a",
"total": 1,
"language": "Japanese"
},
"status": "success"
}
}About the Hobbiesville API
Catalogue Browsing
The API covers two separate catalogue lines — English and Japanese — selectable via a language parameter on every endpoint. list_sets returns an ordered array of {name, code} pairs (newest sets first) matching the store's own Set filter; the code field is the exact value to pass as set_name in search_cards. Similarly, list_rarities and list_finishes expose the rarity and finish vocabularies for one line, each returning {name, code} entries and a total count. All three list endpoints accept an optional query substring for quick filtering.
Card Search and Single-Card Lookup
search_cards is the main retrieval endpoint. It accepts name (fuzzy text), rarity, finish, in_stock, is_hot, sort, page, and limit (capped at 200). Each card object in the cards array carries a conditions[] array with one row per condition — NM, LP, MP for English; five named conditions for Japanese — each including stock, in_stock, stock_status ("In Stock" / "Sold Out"), the sell price in CAD, market price, and buylist cash and credit offers. The response also includes has_more for pagination and a total site match count. get_card retrieves one card by product_id and returns the identical card object shape without needing a search.
Buylist Rules and Pricing Analysis
get_pricing_rules reads the store's published buylist configuration for a given product_line ("Pokemon" or "Pokemon Japanese"). The response surfaces percent_of_retail, base_credit_percent, per-condition condition_overrides, and structured rule_sets with fields like retail_discount, cash_ratio_of_price, and credit_percent. This is the store's own declared logic, not derived data.
get_pricing_model samples up to 800 live listings (4 pages × 200 cards) and fits regression formulas on the spot. It returns a sell_price_model with per-condition ratios and R² values, a buy_price_model broken down by language, condition, and price bracket, and a credit_price_model showing the most common cash-to-credit multipliers. get_set_pricing_formulas does the same analysis set by set — walking up to 8 sets per call — and includes 95% confidence intervals per formula, coverage metadata, and an overall pooled result across all sets in the call.
The Hobbiesville API is a managed, monitored endpoint for hobbiesville.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when hobbiesville.com 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 hobbiesville.com 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?+
- Building a buylist comparison tool that shows Hobbiesville's cash and credit offers alongside market price for any searched Pokémon card
- Tracking per-condition stock availability across English and Japanese sets to alert buyers when a sold-out card comes back in stock
- Deriving sell-price and buy-price regression formulas by set to estimate what Hobbiesville would price a new card at before it appears in the catalogue
- Auditing the store's published buylist pricing rules against actual listed buy prices using get_pricing_rules and get_pricing_model together
- Filtering high-demand cards via the is_hot flag in search_cards to monitor which cards the store currently considers fast-moving
- Cataloguing rarity and finish distributions across a set by combining list_rarities, list_finishes, and search_cards results
- Generating a price-bracket model for Japanese singles using get_set_pricing_formulas with language set to Japanese
| 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.