How Bazaar APIhowbazaar.gg ↗
Access How Bazaar game data via API: items, skills, merchants, and monster encounters with filters by hero, tier, size, and tag.
What is the How Bazaar API?
The How Bazaar API provides 4 endpoints covering the full game database at howbazaar.gg, including items, skills, merchants, and monster encounters. The get_items endpoint alone returns structured data across fields like startingTier, tiers, tags, hiddenTags, customTags, enchantments, quests, and image URLs, with optional filters by hero, size, tier, and tag. This makes it straightforward to query any slice of the game's content catalog programmatically.
curl -X GET 'https://api.parse.bot/scraper/399e59d8-820c-4359-9761-fe29a4de9d62/get_items?tag=Weapon&hero=Vanessa&size=Small&tier=Bronze&query=Sword' \ -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 howbazaar-gg-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.how_bazaar_game_database_api import HowBazaar, Item, Skill, Merchant, MonsterDay, Tier, Size, Hero
client = HowBazaar()
# Search for weapon items belonging to Vanessa at Bronze tier
for item in client.items.search(hero=Hero.VANESSA, tier=Tier.BRONZE, tag="Weapon"):
print(item.name, item.size, item.starting_tier, item.image_url)
# Search skills by name for a specific hero
for skill in client.skills.search(query="Aggressive", hero=Hero.COMMON):
print(skill.name, skill.starting_tier, skill.unified_tooltips)
# List all merchants
for merchant in client.merchants.list():
print(merchant.name, merchant.description, merchant.heroes)
# List monster encounters by day
for day in client.monsterdays.list():
print(day.day, len(day.groups))
Search and filter game items. Returns item details including tier progression tooltips, tags, enchantments, combat encounters, and image URLs. All items are returned when no filters are specified. Supports filtering by name substring, hero, size, starting tier, and tag category.
| Param | Type | Description |
|---|---|---|
| tag | string | Filter by item tag. Matches against tags, hiddenTags, and customTags arrays on each item. |
| hero | string | Filter by hero name. Returns items belonging to the specified hero or to Common. |
| size | string | Filter by item size. |
| tier | string | Filter by starting tier. |
| query | string | Search items by name (case-insensitive substring match). |
{
"type": "object",
"fields": {
"items": "array of item objects with id, name, startingTier, tiers, tags, hiddenTags, customTags, size, heroes, enchantments, quests, unifiedTooltips, combatEncounters, image_url",
"total": "integer count of items in the filtered result"
},
"sample": {
"data": {
"items": [
{
"id": "529a7e95-b350-4fd6-96fd-fef80d4c1462",
"name": "Old Sword",
"size": "Small",
"tags": [
"Weapon"
],
"tiers": {
"Gold": {
"tooltips": [
"Cooldown 5 seconds",
"Deal 20 Damage"
]
},
"Bronze": {
"tooltips": [
"Cooldown 5 seconds",
"Deal 5 Damage"
]
},
"Silver": {
"tooltips": [
"Cooldown 5 seconds",
"Deal 10 Damage"
]
},
"Diamond": {
"tooltips": [
"Cooldown 5 seconds",
"Deal 40 Damage"
]
},
"Legendary": {
"tooltips": []
}
},
"heroes": [
"Common"
],
"quests": [],
"image_url": "https://howbazaar-images.b-cdn.net/images/items/529a7e95-b350-4fd6-96fd-fef80d4c1462.avif",
"customTags": [],
"hiddenTags": [
"Damage"
],
"enchantments": [
{
"type": "Golden",
"tooltips": [
"This has double value."
]
}
],
"startingTier": "Bronze",
"unifiedTooltips": [
"Cooldown 5 seconds",
"Deal (5/10/20/40) Damage"
],
"combatEncounters": [
{
"cardId": "41c5f103-2d76-4a51-ae28-ee294490b071",
"cardName": "Ventriloquist"
}
]
}
],
"total": 7
},
"status": "success"
}
}About the How Bazaar API
Items and Skills
The get_items endpoint returns an array of item objects with fields including id, name, startingTier, tiers, tags, hiddenTags, customTags, size, heroes, enchantments, quests, and unifiedTooltips. You can filter by tag (matched against all three tag arrays), hero, size (Small, Medium, Large), tier (Bronze through Legendary), or a case-insensitive substring query on the item name. Calling it without any filters returns every item in the database along with a total count.
The get_skills endpoint mirrors this structure for skills, returning objects with id, name, startingTier, tiers, tags, hiddenTags, customTags, size, heroes, artKey, unifiedTooltips, and combat encounter data. It accepts the same hero, tier, and query filters. Both endpoints include image URLs, making them suitable for building visual reference tools.
Merchants and Monsters
The get_merchants endpoint takes no inputs and returns all in-game merchants with fields id, name, heroes, description, filters, and image_url. The filters field describes each merchant's sale configuration — which items or categories they deal in — making it useful for building shop-lookup tools or hero-specific merchant guides.
The get_monsters endpoint returns encounter data organized by game day. Each entry in the days array includes a day number and a groups array of monster encounters. Each encounter carries cardId, cardName, health, items, skills, and image_url. This structure lets you reconstruct the full encounter progression for a given run or display what a player can expect to face on any specific day.
The How Bazaar API is a managed, monitored endpoint for howbazaar.gg — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when howbazaar.gg 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 howbazaar.gg 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 an item browser filtered by hero and tier for min-maxing build planning
- Generate a merchant directory showing which merchants serve each hero and what their sale filters cover
- Create a monster encounter timeline by consuming the
daysarray fromget_monsters - Display skill tooltips and artwork in a fan wiki or companion app using
unifiedTooltipsand image URLs - Cross-reference item enchantments with skills to identify synergies for a given hero
- Power a search-as-you-type item or skill lookup using the case-insensitive
queryparameter - Filter all Bronze-tier weapons for a specific hero to produce new-player gear guides
| 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 How Bazaar have an official developer API?+
How does hero filtering work across `get_items` and `get_skills`?+
hero string parameter. When set, results include items or skills that belong to the specified hero as well as those tagged as Common, since Common items are available to all heroes. Omitting the parameter returns data across all heroes.Does the API return player account data, run history, or leaderboard stats?+
Are there pagination controls for large result sets from `get_items`?+
total count alongside the full results array. There are no pagination parameters like page or limit in the current implementation — all matching records are returned in a single response. You can fork the API on Parse and revise it to add offset-based or cursor-based pagination.What does the `tiers` field on an item contain versus `startingTier`?+
startingTier is the base rarity tier at which an item enters the game (e.g., Bronze, Silver). The tiers field is an array containing the tier-specific variants of the item, each with its own tooltip and stat data, representing the item's full upgrade path.