Lashinbang APIshop.lashinbang.com ↗
Search and retrieve secondhand anime figures, games, doujinshi, and more from Lashinbang's online catalog via 3 structured JSON endpoints.
What is the Lashinbang API?
The Lashinbang Shop API provides 3 endpoints to search, filter, and retrieve product data from Lashinbang's secondhand anime merchandise catalog. The search_products endpoint returns paginated results with 12 fields per item including price, condition, maker, series, and store location. Use get_product_detail for full condition notes and JAN codes on individual listings, or get_categories to enumerate valid filter values before querying.
curl -X GET 'https://api.parse.bot/scraper/9c789f40-84ff-4824-bd15-c6b3e6aa4f68/search_products?page=1&sort=arrival&limit=20&state=2&category=%E6%9B%B8%E7%B1%8D' \ -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 shop-lashinbang-com-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.
"""Walkthrough: Lashinbang SDK — search secondhand anime goods and drill into details."""
from parse_apis.lashinbang_online_shop_api import (
Lashinbang, Sort, Category, Condition, ProductNotFound
)
client = Lashinbang()
# Discover available filter options (categories and condition states)
filters = client.filteroptionses.get()
print(filters.note)
for cat in filters.categories:
print(cat.name, cat.has_numeric_id)
# Search for figures in the goods category, sorted by newest arrivals
for item in client.productsummaries.search(
keyword="フィギュア",
category=Category.GOODS,
sort=Sort.ARRIVAL,
state=Condition.UNOPENED,
limit=5,
):
print(item.title, item.price, item.maker, item.store)
# Drill into full product details from a search result
item = client.productsummaries.search(keyword="鬼滅の刃", limit=1).first()
if item:
detail = item.details()
print(detail.title, detail.price, detail.condition, detail.jan_code)
# Typed error handling for a missing product
try:
bad_item = client.productsummaries.search(keyword="テスト", limit=1).first()
if bad_item:
bad_item.details()
except ProductNotFound as exc:
print(f"Product not found: {exc.product_id}")
print("exercised: filteroptionses.get / productsummaries.search / details / ProductNotFound")
Search products on Lashinbang online shop by keyword, category, condition state, and sorting. Returns paginated results with product details including price, condition, maker, series, and store information. Paginates via integer page number. Each item carries enough metadata to filter client-side by series, maker, or store.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-based). |
| sort | string | Sort order for results. |
| limit | integer | Number of results per page, between 1 and 100. |
| state | string | Product condition filter. |
| keyword | string | Search keyword (Japanese text). E.g. フィギュア, 鬼滅の刃, ツイステ. |
| category | string | Main category filter. |
{
"type": "object",
"fields": {
"items": "array of product summary objects with id, title, url, image, price, condition, category, subcategory, series, maker, store, jan_code",
"last_page": "integer total number of pages",
"total_hits": "integer total number of matching products",
"current_page": "integer current page number"
},
"sample": {
"data": {
"items": [
{
"id": "6059086",
"url": "https://shop.lashinbang.com/products/detail/6059086",
"image": "https://img.lashinbang.com/product_669100c2abb02.JPG",
"maker": "バンダイ",
"price": 13376,
"store": "熊本店",
"title": "フィギュアーツZERO 範馬刃牙 ビスケット・オリバ 【フィギュア】[バンダイ]",
"series": "グラップラー刃牙",
"category": "グッズ",
"jan_code": "4543112762399",
"condition": "B",
"subcategory": "フィギュア"
}
],
"last_page": 30195,
"total_hits": 150973,
"current_page": 1
},
"status": "success"
}
}About the Lashinbang API
Search and Filter Secondhand Listings
The search_products endpoint accepts up to six parameters: keyword (Japanese text such as フィギュア or 鬼滅の刃), category, state (product condition), sort, limit (1–100 per page), and page. Each item in the items array carries id, title, url, image, price (yen integer), condition, category, subcategory, series, maker, store, and jan_code. The response also includes total_hits and last_page so you can page through large result sets programmatically.
Product Detail
get_product_detail takes a numeric product_id — obtainable from items[*].id in search results — and returns the full record for a single listing. The description field contains the store's raw condition notes, including any disclosed defects or remarks. Other fields include category, jan_code, condition, price, store, and a direct url and image link.
Category and Condition Discovery
get_categories takes no inputs and returns two arrays: categories (Japanese-text identifiers, not numeric IDs) and states (numeric condition filters with human-readable names). The response includes a note field clarifying the category identifier system. Run this endpoint first to build valid filter sets for search_products, since category values are Japanese strings and condition values are integers.
The Lashinbang API is a managed, monitored endpoint for shop.lashinbang.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when shop.lashinbang.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 shop.lashinbang.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?+
- Track price trends for specific anime figure series by polling
search_productswith a series keyword over time - Build a collector's watchlist app that alerts users when a specific maker or series appears in new listings
- Aggregate JAN codes from
get_product_detailto cross-reference Lashinbang listings against other secondhand marketplaces - Filter listings by condition state using
get_categoriesstates to surface only near-mint items for price comparison - Populate a doujinshi catalog with title, store, and condition data from paginated
search_productsresults - Index store-level inventory by grouping
storefields across search results to compare which locations carry specific categories - Validate barcode data by extracting
jan_codefields from individual product detail pages
| 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 Lashinbang have an official developer API?+
What does `get_product_detail` return that `search_products` does not?+
description field — containing raw store notes about item condition and any disclosed defects — is only available via get_product_detail. Search results carry a summary condition label but not the full freeform remarks the store attaches to the listing.Are sold-out or historical listings accessible through this API?+
search_products and get_product_detail results.Can I retrieve seller ratings, review scores, or buyer feedback for listings?+
How do category identifiers work in `get_categories`?+
note field that explains this system. Condition (state) filters use numeric values. Passing a category string from get_categories directly into the category parameter of search_products is the intended workflow.