Suruga-ya APIsuruga-ya.jp ↗
Access product details, condition definitions, and search results from Suruga-ya, Japan's second-hand goods marketplace. 4 endpoints covering prices, buyback values, and branch numbers.
What is the Suruga-ya API?
The Suruga-ya API provides 4 endpoints for querying product data from suruga-ya.jp, a Japanese second-hand goods marketplace. The get_branch_definitions endpoint returns all 207 known branch_number-to-condition mappings used across listings, while search_products delivers paginated results with price, condition, brand, and image URL for any keyword or product ID.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/c15ae5c1-0b6b-476c-b6d4-18a0e104fcb9/get_branch_definitions' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace suruga-ya-jp-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.suruga_ya_product_conditions_api import Surugaya, Sort, Category, ProductSummary, Product, BranchDefinition
client = Surugaya()
# Look up a specific branch number definition
branch = client.branchdefinitions.get(branch_number="0076")
print(branch.branch_number, branch.definition, branch.is_used, branch.source)
# Get all definitions as a set
defset = client.branchdefinitionsets.get_all()
print(defset.total, len(defset.definitions))
# Search for products with sorting and category filter
for item in client.productsummaries.search(search_word="ガンダム", sort=Sort.PRICE_ASC, category=Category.GAMES):
print(item.product_id, item.title, item.price, item.condition)
# Drill into full product detail
detail = item.details()
print(detail.product_name, detail.condition_type, detail.buyback_price, detail.url)
break
# Fetch a product directly by ID
product = client.products.get(product_id="112000127")
print(product.product_name, product.condition_type, product.condition_detail, product.url)
Returns all 207 known branch_number definitions (0001-0207) that map to product conditions on suruga-ya.jp. Branch numbers represent the condition/state variant of a used product listing. Numbers 9000-9999 are generic marketplace seller listings, and numbers beyond 0207 are generic used condition. The response is a static mapping — no network call is made.
No input parameters required.
{
"type": "object",
"fields": {
"notes": "object with explanatory notes about special ranges (0001, 9000-9999, 0208+)",
"total": "integer - count of defined branch numbers (207)",
"definitions": "object mapping branch_number strings (0001-0207) to their Japanese condition labels"
},
"sample": {
"data": {
"notes": {
"0001": "Default listing (new/used standard condition)",
"0208+": "Numbers beyond 0207 that are not explicitly defined typically map to generic 中古 (used)",
"9000-9999": "Marketplace seller listings (マケプレ) - generic used condition, seller provides specific condition description"
},
"total": 207,
"definitions": {
"0001": "新品/中古（通常）",
"0076": "Aランク",
"0207": "標準"
}
},
"status": "success"
}
}About the Suruga-ya API
Product Condition System
Suruga-ya uses a 4-digit branch_number to identify the condition variant of a used product listing. get_branch_definitions returns the full static mapping of all 207 defined numbers (0001–0207) as Japanese condition labels, plus explanatory notes on special ranges: 9000–9999 indicates generic marketplace seller listings, and numbers above 0207 fall back to a generic used-condition label. lookup_branch_number resolves a single branch number and returns definition (the Japanese label), is_used (boolean), and a source field indicating whether the result came from a static_mapping, a range_rule, or was not_found.
Product Detail Retrieval
get_product_detail accepts a required product_id (numeric string from the product URL) and optional branch_number and store_id parameters. The response includes product_name, condition_type (e.g. 中古, 新品), condition_detail extracted from the product name, a prices object with new_price and/or used_price as integers in yen, buyback_price for trade-in value, and a branch_definition field that maps the branch number to its known Japanese label. Omitting branch_number returns the default online listing; supplying store_id (the tenpo_cd value) targets a specific physical store's listing.
Search and Filtering
search_products takes a required search_word (Japanese or English keyword, or a product ID), with optional page, sort, and category filter parameters. Each page returns up to 24 items, each containing product_id, title, category, condition, price, brand, release_date, and image_url. The total_count field tells you the full result set size for building pagination. Passing an empty string for category searches across all categories.
The Suruga-ya API is a managed, monitored endpoint for suruga-ya.jp — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when suruga-ya.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 suruga-ya.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?+
- Build a price tracker that monitors used game or anime merchandise prices on Suruga-ya using
search_productsandget_product_detail. - Decode condition labels on scraped Suruga-ya listings by resolving branch numbers through
lookup_branch_number. - Compare buyback (
buyback_price) versus resale (used_price) margins for specific product IDs. - Aggregate category-filtered search results to analyze second-hand inventory volume and pricing trends.
- Display store-specific listings by passing a
store_idtoget_product_detailfor a physical Suruga-ya branch. - Enumerate all 207 branch condition definitions via
get_branch_definitionsto localize or translate condition labels for a non-Japanese audience. - Identify marketplace seller listings (branch numbers 9000–9999) separately from direct Suruga-ya store stock.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Suruga-ya have an official public developer API?+
What does `lookup_branch_number` return for a branch number outside the 0001–0207 range?+
source set to range_rule. Numbers above 0207 that are not in a known range return a generic used-condition label. Numbers that match no rule at all return source: not_found with is_used and definition both null.Does `search_products` return seller reviews or rating data?+
search_products includes product_id, title, category, condition, price, brand, release_date, and image_url. Seller ratings and review counts are not part of the response. You can fork the API on Parse and revise it to add a reviews or ratings endpoint if that data is accessible on the product page.Can I retrieve historical price data or price change history for a product?+
get_product_detail. Historical pricing is not exposed. You can fork the API on Parse and revise it to add a price history endpoint if you want to store and query snapshots over time.How does pagination work in `search_products`?+
items_per_page: 24) and includes a total_count integer. Increment the page parameter to walk through subsequent pages. If total_count is 240, there are 10 pages of results.