hpoi.net APIhpoi.net ↗
Search and retrieve anime figure data from Hpoi.net. Get item details, gallery images, manufacturer info, user comments, and collection counts via 6 endpoints.
curl -X GET 'https://api.parse.bot/scraper/4f2b435c-3a22-4499-85bc-34799427b3fe/search_items?page=1&keyword=%E5%88%9D%E9%9F%B3&category=100' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for collectible items in the Hpoi database with filters. Returns paginated results sorted by the specified order.
| Param | Type | Description |
|---|---|---|
| r18 | integer | R18 filter: -1 (all), 0 (non-R18), 1 (R18) |
| page | integer | Page number |
| order | string | Sort order: add (newest added), release (by release date), hot (popularity), weekhot, dayhot, score (rating) |
| keyword | string | Search keyword |
| category | integer | Category ID: 100 (手办), 200 (动漫模型), 300 (Doll娃娃), 400 (毛绒布偶), 500 (真实模型), 600 (GK/DIY), 10000 (All) |
{
"type": "object",
"fields": {
"page": "integer current page number",
"items": "array of item objects with id, name, thumbnail, manufacturer, release_date, added_date"
},
"sample": {
"data": {
"page": 1,
"items": [
{
"id": "123943",
"name": "雪未来2026 收藏",
"thumbnail": null,
"added_date": null,
"manufacturer": "",
"release_date": null
}
]
},
"status": "success"
}
}About the hpoi.net API
The Hpoi.net API exposes 6 endpoints for querying the Hpoi collectible anime figure database, covering item search, detailed product specs, gallery images, user comments, and manufacturer profiles. The get_item_detail endpoint returns structured attributes like scale, material, series, character, release date, and collection counts broken down by want, owned, preorder, and following — everything needed to build a figure tracker or catalog browser.
Item Search and Filtering
The search_items endpoint accepts a keyword param alongside filters for category, r18 status, and order. Category IDs cover the major collectible types tracked on Hpoi: 手办 (figures, ID 100), 动漫模型 (anime models, 200), Doll娃娃 (dolls, 300), 毛绒布偶 (plush, 400), 真实模型 (real models, 500), GK/DIY (600), and a catch-all (10000). Sort options include add, release, hot, weekhot, dayhot, and score. Results are paginated and each item in the array includes id, name, thumbnail, manufacturer, release_date, and added_date.
Item Detail and Gallery
get_item_detail takes a numeric item ID and returns the full product record: a score rating, cover images, a structured attributes object (name, series, character, material, scale, and more), and fav_counts with four distinct collection-status counts. Crucially, the response also includes a node_id string that is required as input for both get_item_comments and get_item_gallery. The get_item_gallery endpoint uses an offset parameter as an absolute image index — requesting an offset beyond the available image count returns an empty array, so iterate until the array is empty to paginate fully.
Comments and Community Data
get_item_comments accepts the node_id and an optional page number, returning deduplicated comments with author, text, and time fields. This allows tracking community sentiment and user discussion per item without any additional authentication.
Manufacturer Data
get_manufacturer_list returns all popular manufacturers with their id, name, item count, and average score — no inputs required. get_manufacturer_detail accepts a manufacturer id (for example, 18 for Good Smile Company) and a page number, returning the manufacturer's Chinese name, a description info string, and a list of highlighted items with id, name, and thumbnail. Note that these items represent featured products, not the full paginated catalog.
- Build a personal anime figure collection tracker using fav_counts (want, owned, preorder, following) from get_item_detail
- Aggregate new release announcements by polling search_items with order=release and filtering by category
- Compare manufacturer ratings and item counts from get_manufacturer_list to analyze market share across figure makers
- Display community sentiment for a figure by fetching paginated comments via get_item_comments using the node_id
- Build a figure image gallery viewer by paginating get_item_gallery with the offset parameter until an empty array is returned
- Filter and surface R18 or non-R18 figure listings separately using the r18 parameter in search_items
- Sync a local database of figure specs (scale, material, series, character) using attributes from get_item_detail
| 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 | 250 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 Hpoi.net have an official developer API?+
Why does get_item_gallery require both item_id and node_id?+
id field and the node_id field — and they must correspond to the same item. Mismatched pairs will not return valid results.Does the API expose secondary market prices or auction listings for figures?+
Is there a way to retrieve a manufacturer's full product catalog, not just featured items?+
What does the score field in get_item_detail represent, and can it be null?+
score field is a string representing the community rating for the item on Hpoi. It is returned as null when an item has not yet received enough ratings to display a score.