Dofusroom APIdofusroom.com ↗
Access 3,200+ Dofus equipment items via 6 endpoints. Query stats, crafting recipes, set membership, and category counts by level, name, or category.
What is the Dofusroom API?
The Dofusroom API provides structured access to Dofus game equipment data across 6 endpoints, covering over 3,200 items. Use list_equipment to page through gear sorted by level, get_item_details to retrieve full stat blocks and set associations, or get_item_recipe to pull crafting resource requirements for any item. Level filters, name search, and category filtering are available across most endpoints.
curl -X GET 'https://api.parse.bot/scraper/cdd857b5-cf43-4a51-837d-2df7e2934b53/list_equipment?limit=5&offset=0&category=equipements&max_level=200&min_level=1' \ -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 dofusroom-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.
from parse_apis.dofusroom_encyclopedia_api import DofusRoom, ItemSummary, Item, Category, ItemWithRecipe
client = DofusRoom()
# Search for items by name
results = client.itemsummaries.search(query="Psychopump", category=Category.EQUIPEMENTS)
for summary in results:
print(summary.name, summary.level, summary.type)
# Get full details for the first result
detail = summary.details()
print(detail.name, detail.real_type, detail.level)
for stat_key, stat_value in detail.stats.items():
print(stat_key, stat_value)
# Get recipe for the item
recipe = detail.recipe.get()
print(recipe.has_recipe, recipe.item_name)
for resource in recipe.resources:
print(resource.name, resource.quantity)
# List equipment with recipes included
crafted_items = client.itemwithrecipes.list(category=Category.ARMES, min_level="190", max_level="200")
for item in crafted_items:
print(item.name, item.level, item.set_name)
for res in item.resources:
print(res.name, res.quantity, res.image_url)
# Get category counts
counts = client.categorycountses.get()
print(counts.counts["equipements"], counts.counts["armes"])
List equipment items with pagination and optional filters. Returns item IDs, names, types, levels, and set information. Items are sorted by level descending. Supports offset-based pagination via the offset param.
| Param | Type | Description |
|---|---|---|
| name | string | Filter by item name (partial match) |
| limit | integer | Number of items to return (max ~50) |
| offset | integer | Pagination offset |
| category | string | Item category to list |
| max_level | string | Maximum level filter (1-200) |
| min_level | string | Minimum level filter (1-200) |
{
"type": "object",
"fields": {
"count": "integer - number of items returned",
"items": "array of item summary objects with id, name, type, level, set_name, set_id",
"limit": "integer - limit used",
"offset": "integer - pagination offset used",
"category": "string - the category queried"
},
"sample": {
"data": {
"count": 5,
"items": [
{
"id": 4581,
"name": "Potbellion Collar",
"type": "Amulet",
"level": 200,
"set_id": 624,
"set_name": "Armarines Set"
}
],
"limit": 5,
"offset": 0,
"category": "equipements"
},
"status": "success"
}
}About the Dofusroom API
Equipment Browsing and Search
The list_equipment endpoint returns paginated item summaries — id, name, type, level, set_name, and set_id — sorted by level descending. Narrow results using min_level and max_level (both accept 1–200), a partial name string, or a category slug. Pagination is offset-based via the offset parameter with a per-request cap of roughly 50 items. The search_items endpoint targets the same fields but is optimized for name lookups with partial matching, and also accepts the same level and category filters.
Item Details and Stats
get_item_details accepts an item_id from any listing endpoint and returns the complete stat block for that item: a stats object mapping stat keys to human-readable descriptions, a caracs array of characteristics, equipment conditions as an array of strings, the localized real_type, and a set object containing setId, setName, and ankamaSetId when the item belongs to a set. Items not in a set return an empty array for set.
Crafting Recipes
get_item_recipe returns the crafting recipe for a given item ID. The response includes a resources array of objects with name, quantity, and image_url for each ingredient, plus a has_recipe boolean. Items with no recipe return has_recipe: false and an empty resources array. The list_equipment_with_recipes endpoint combines a listing query and per-item recipe lookups in a single call; keep the limit parameter small (the default is 10) to stay within response time budgets.
Category Inventory
get_category_counts requires no parameters and returns a counts object mapping every top-level category (equipements, armes, ressources, consommables, creatures, panoplies) and their subcategories to item count strings. This is useful for building category navigation or validating filter values before running heavier listing queries.
The Dofusroom API is a managed, monitored endpoint for dofusroom.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when dofusroom.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 dofusroom.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?+
- Build a gear planner that filters equipment by level range using
min_levelandmax_leveland displays stat blocks fromget_item_details. - Calculate total crafting materials for a full equipment set by batching
get_item_recipecalls and summingquantityvalues across theresourcesarrays. - Populate a category browser showing item counts per subcategory using data from
get_category_counts. - Implement an in-game item search tool using
search_itemswith partial name matching and category filtering. - Display set bonus context by reading
set_nameandset_idfields from listing results and linking to set-level views. - Automate crafting cost estimation by combining recipe resource names and quantities with external price data for each ingredient.
- Index all items across levels for offline search by paginating
list_equipmentwith incrementingoffsetvalues.
| 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 Dofusroom have an official developer API?+
What does `get_item_details` return beyond basic stats?+
get_item_details returns the full stats object with human-readable descriptions keyed by stat type, a caracs array, an array of conditions strings that describe any equipment requirements, and a set object with setId, setName, and ankamaSetId when the item belongs to a named set. Items outside a set return an empty array for the set field.Can I retrieve all items in a single request?+
list_equipment caps results at roughly 50 items per call and uses offset-based pagination. To retrieve all items in a category, increment the offset parameter across multiple requests. get_category_counts can tell you the total item count per category before you start paginating.Does the API cover live market prices or auction house data for items?+
Are monster drop sources included in recipe or item detail responses?+
get_item_recipe lists crafting ingredients with name, quantity, and image URL, but does not include monster drop sources or loot tables for acquiring those ingredients. You can fork this API on Parse and revise it to add a drops endpoint covering that data.