BazaarDB APIbazaardb.gg ↗
Search and retrieve card data from BazaarDB.gg. Access items, skills, merchants, monsters, events with tiers, attributes, tooltips, and enchantments.
What is the BazaarDB API?
The BazaarDB.gg API exposes 2 endpoints for accessing card data from The Bazaar game database, covering items, skills, merchants, trainers, monsters, and events. The search_cards endpoint returns paginated card listings with full tier breakdowns, base attributes, enchantments, tags, and hero associations, while get_card retrieves a single card by name with drop sources and per-tier tooltip overrides.
curl -X GET 'https://api.parse.bot/scraper/49e1e7c5-ab05-423d-9afa-ac05d9f04241/search_cards?page=0&limit=5&order=ascending&query=sword&sort_by=Auto&category=all&show_unobtainable=False' \ -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 bazaardb-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.
"""Walkthrough: BazaarDB SDK — search cards, filter by category, get details."""
from parse_apis.Bazaar_DB_API import BazaarDB, Category, Sort, Order, CardNotFound
client = BazaarDB()
# Search for weapon-related items, sorted by name
for card in client.cards.search(query="sword", category=Category.ITEMS, sort_by=Sort.NAME, limit=3):
print(card.name, card.size, card.base_tier)
# Drill down: get the first skill card and inspect its tooltips
skill = client.cards.search(category=Category.SKILLS, limit=1).first()
if skill:
print(skill.name, skill.type, skill.heroes)
for tip in skill.tooltips:
print(tip.text, tip.type)
# Fetch a specific card by name and explore its tiers and enchantments
soap = client.cards.get(name="Bar of Soap")
print(soap.name, soap.base_tier, soap.size)
for drop in soap.dropped_by:
print(drop.title, drop.tier, drop.available)
# Typed error handling: attempt to fetch a non-existent card
try:
client.cards.get(name="Nonexistent Widget XYZ")
except CardNotFound as exc:
print(f"Card not found: {exc.name}")
print("exercised: cards.search / cards.get / tooltips / dropped_by / CardNotFound")
Search and list cards with optional text search, category filtering, and pagination. Returns rich card data including all tiers, base attributes, tooltips, enchantments, tags, heroes, and art URLs. Paginates via page number (0-indexed). Each Card includes full detail: tiers, enchantments, tooltips, drop sources.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (0-indexed) |
| limit | integer | Maximum number of cards to return per page |
| order | string | Sort order |
| query | string | Text search query (e.g. 'sword', 'poison') |
| sort_by | string | Sort field |
| category | string | Card category filter |
| show_unobtainable | boolean | Include unobtainable cards in results |
{
"type": "object",
"fields": {
"page": "integer current page number",
"cards": "array of card objects with full details",
"count": "integer number of cards returned in this response",
"limit": "integer requested limit",
"total": "integer total number of matching cards"
},
"sample": {
"data": {
"page": 0,
"cards": [
{
"id": "e5af5b7c-2e8f-4135-8e14-8d1ea71908de",
"art": "https://s.bazaardb.gg/v1/z15.0/[email protected]?v=6",
"uri": "/card/160zpnfd7sbn7y77326jz1zl77j/Sword-of-Swords",
"name": "Sword of Swords",
"size": "Medium",
"tags": [
"Item",
"Medium",
"Weapon"
],
"type": "Item",
"tiers": {
"Diamond": {
"active_tooltips": [
0,
1
],
"override_attributes": {}
},
"Legendary": {
"active_tooltips": [
0,
1
],
"override_attributes": {}
}
},
"heroes": [
"Common"
],
"quests": null,
"tooltips": [
{
"text": "Deal {ability.0} Damage",
"type": "Active",
"condition": null
}
],
"art_large": "https://s.bazaardb.gg/v1/z15.0/[email protected]",
"base_tier": "Legendary",
"transform": null,
"dropped_by": [
{
"day": 10,
"tier": "Legendary",
"title": "Morguloth",
"available": "Day 10"
}
],
"hidden_tags": [
"Damage"
],
"display_tags": [
"Weapon",
"Relic"
],
"enchantments": {
"Golden": {
"tags": [],
"tooltips": [
"This has double value"
]
}
},
"base_attributes": {
"BuyPrice": 64,
"Multicast": 1,
"SellPrice": 32,
"CooldownMax": 5000,
"DamageAmount": 150
},
"tooltip_replacements": {
"{ability.0}": {
"Fixed": 150
}
}
}
],
"count": 5,
"limit": 5,
"total": 7
},
"status": "success"
}
}About the BazaarDB API
What the API Returns
Both endpoints return rich card objects drawn from the BazaarDB.gg database. Each card includes fields like id, name, type, size, base_tier, heroes, tags, base_attributes, and art (a direct URL to the card's artwork). The tiers field is a nested object mapping tier names to their specific override_attributes and active_tooltips, letting you compare how a card scales from Bronze through Diamond without making additional requests.
Searching and Filtering Cards
The search_cards endpoint accepts a query string for text-based lookup (e.g., 'poison', 'sword') and a category filter to narrow results to one of seven types: all, items, skills, merchants, trainers, monsters, or events. Pagination is controlled via page (0-indexed) and limit, with total in the response telling you the full match count. Results can be sorted by fields such as Name, Size, or Cooldown in either ascending or descending order. The optional show_unobtainable boolean controls whether cards not currently in the game's loot pool appear in results.
Fetching a Single Card
The get_card endpoint takes a card name (e.g., 'Bar of Soap', 'Sword of Swords') and returns the full card record including quests data when available, the card's uri path on BazaarDB.gg, and enriched detail data where the source provides it. This is the right endpoint when you need complete per-tier information for a specific card without iterating through paginated search results.
Coverage Scope
The database covers cards from The Bazaar, an auto-battler game by Tempo. Cards are categorized by type and associated with specific heroes via the heroes array field. Tag strings (e.g., weapon, poison, shield) are returned alongside each card for further client-side filtering.
The BazaarDB API is a managed, monitored endpoint for bazaardb.gg — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bazaardb.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 bazaardb.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 a deck-builder tool that filters cards by category, hero, and tags using
search_cards. - Display per-tier stat progressions for any card using the
tiersobject withoverride_attributes. - Populate a searchable item wiki with card art URLs, size, and tooltip text from
get_card. - Identify all monster cards available to a specific hero by filtering on
typeandheroesfields. - Compare cooldown values across skills by sorting
search_cardsresults byCooldowndescending. - Track which cards are currently obtainable versus unobtainable using the
show_unobtainableparam. - Fetch drop source information for crafting guides using the enriched data returned by
get_card.
| 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 BazaarDB.gg have an official developer API?+
What does the `tiers` field in a card response actually contain?+
tiers field is a nested object keyed by tier name (e.g., Bronze, Silver, Gold, Diamond). Each tier entry contains override_attributes, which are the stat changes that apply at that tier relative to the base, and active_tooltips, which are the ability or effect descriptions active at that tier. This lets you see exactly how a card's stats and abilities evolve across tiers in a single response.Can I look up cards by hero name or tag rather than text query?+
search_cards endpoint supports text search via query and category filtering via category, but does not currently accept hero name or tag as a direct filter parameter. The heroes and tags arrays are returned on each card object, so you can retrieve a broad result set and filter client-side. You can fork this API on Parse and revise it to add a dedicated hero or tag filter parameter.Does the API include player account data, match history, or leaderboard information?+
How should I handle pagination when retrieving all cards?+
search_cards endpoint returns total (total matching cards), count (cards in the current page), page (current 0-indexed page), and limit (page size). To paginate through all results, increment page until the sum of returned count values equals total. Setting a higher limit reduces the number of round trips needed.