RustClash APIwiki.rustclash.com ↗
Access Rust game items, skins, blueprints, and crafting data via the RustClash Wiki API. Search items, get stats, recipes, loot tables, and skin prices.
What is the RustClash API?
The RustClash Wiki API provides structured access to Rust game data across 8 endpoints, covering items, skins, blueprints, and crafting recipes. The get_item_details endpoint returns per-item stats, crafting recipes, repair costs, loot locations, recycling outputs, and workbench tier data. The list_skins endpoint exposes skin pricing in USD, Twitch drop flags, and new-release flags across the full skin catalog.
curl -X GET 'https://api.parse.bot/scraper/d6c9865e-42a0-40de-bffc-3fa158c5a795/search_items?query=ak47' \ -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 wiki-rustclash-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.rust_clash_wiki_api import RustClashWiki, SkinSort, ItemNotFound
wiki = RustClashWiki()
# Search for weapons by keyword
for result in wiki.items.search(query="shotgun"):
print(result.name, result.type, result.slug)
# List all item groups/categories
for group in wiki.itemgroups.list():
print(group.name, group.group)
# List items in a specific group via constructible ItemGroup
weapons_group = wiki.itemgroup(group="weapons")
for item_summary in weapons_group.items.list():
print(item_summary.name, item_summary.slug)
# Get full item details directly
rifle = wiki.items.get(slug="assault-rifle")
print(rifle.name, rifle.description)
for stat_name, stat_value in rifle.stats.items():
print(stat_name, stat_value)
# Navigate from summary to detail
for item_summary in wiki.itemgroup(group="tools").items.list(limit=3):
detail = item_summary.details()
print(detail.name, detail.description)
# List skins sorted by price, filtered by item
for skin in wiki.skins.list(sort=SkinSort.PRICE, item_filter="Assault Rifle"):
print(skin.name, skin.item, skin.price_usd, skin.is_new)
# Get skin detail and check prices
skin_detail = wiki.skins.get(slug="aircraft-parts-ak47")
print(skin_detail.name, skin_detail.description)
for price in skin_detail.prices:
print(price.source, price.price)
# Navigate from skin summary to detail
for skin_summary in wiki.skins.list(sort=SkinSort.NAME, limit=2):
full_skin = skin_summary.details()
print(full_skin.name, full_skin.stats)
# Featured skins from the homepage
for featured in wiki.skins.featured():
print(featured.name, featured.slug, featured.price)
# Blueprint tracker - all tiers
for tier in wiki.blueprinttiers.list():
print(tier.tier, tier.count)
for bp_item in tier.items:
print(bp_item.name, bp_item.scrap_cost)
Full-text search across items and skins by keyword. Returns up to 10 results mixing both items and skins, each with name, slug, type, URL, and image. Use the slug from results to fetch full details via get_item_details or get_skin_details depending on the type field.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g. 'ak47', 'wood', 'shotgun'). |
{
"type": "object",
"fields": {
"count": "integer total number of results returned",
"results": "array of search result objects with name, slug, type, url, and image fields"
},
"sample": {
"data": {
"count": 10,
"results": [
{
"url": "https://wiki.rustclash.com/skin/aircraft-parts-ak47",
"name": "Aircraft Parts AK47",
"slug": "aircraft-parts-ak47",
"type": "skin",
"image": "https://wiki.rustclash.com/img/skins/20/21701.png"
}
]
},
"status": "success"
}
}About the RustClash API
Item Discovery and Detail
The search_items endpoint accepts a query string and returns up to 10 mixed results containing both items and skins, each with name, slug, type, url, and image fields. For category browsing, list_items accepts a group parameter — valid values include weapons, resources, clothing, tool, and build — and returns all items in that group. list_all_item_groups retrieves the full set of available group identifiers from the site navigation, useful for discovering valid group values dynamically.
Item Stats and Crafting Data
get_item_details is the most data-dense endpoint. It accepts an item slug (e.g. assault-rifle, pump-shotgun) and returns a stats object of key-value pairs, a description string, and a tabs object keyed by tab ID. Tab IDs include loot (where the item drops), craft (materials and workbench tier), blueprint (research costs), repair, recycle, damage, mods, skins, and tech-tree. The get_blueprint_tracker endpoint requires no inputs and returns all craftable items organized by workbench tier, with each item's scrap_cost included.
Skin Catalog and Pricing
list_skins returns the full skin catalog with optional sort (by index, price, name, or item) and item_filter for case-insensitive partial matching against the associated item name. Each skin object includes price_usd, is_twitch_drop, is_new, slug, and image. get_skin_details accepts a skin slug and returns a stats object (including Workshop ID, Marketable, and Skin Category), a prices array with per-source price objects, and tabs such as buy-skin, reskin, and break-skin. The list_featured_skins endpoint returns two ranked arrays — newest_skins and most_expensive_skins — each with name, slug, and price.
The RustClash API is a managed, monitored endpoint for wiki.rustclash.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wiki.rustclash.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 wiki.rustclash.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 Rust crafting assistant that pulls workbench tier, required materials, and scrap costs from
get_item_detailsandget_blueprint_tracker. - Create a skin price tracker by polling
list_skinswithsort=priceand monitoring changes inprice_usdvalues over time. - Populate a loot table reference tool using the
loottab data returned byget_item_detailsfor each weapon or resource slug. - Build a Rust item search autocomplete using
search_itemsto match user input against item and skin names with associated images. - Generate a blueprint research checklist organized by workbench tier using the
tiersarray fromget_blueprint_tracker. - Filter and display all Twitch drop skins by checking the
is_twitch_dropflag inlist_skinsresults. - Show skin reskin and break-down options in a loadout tool using the
reskinandbreak-skintabs fromget_skin_details.
| 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 RustClash Wiki have an official developer API?+
What does `get_item_details` return beyond basic stats?+
stats object of key-value pairs, a description string, and a tabs object keyed by tab ID. The tabs can include loot, craft, blueprint, repair, recycle, damage, mods, skins, tech-tree, and tips, though not every item has every tab populated.Does `list_skins` support pagination?+
list_skins returns all skins in a single response, filtered and sorted client-side based on the sort and item_filter parameters. For large catalogs this means a single potentially large response with no page or offset controls. You can fork this API on Parse and revise it to add pagination if your use case requires chunked delivery.Does the API expose historical skin price data or price trends over time?+
price_usd values from list_skins and per-source prices arrays from get_skin_details, but no historical snapshots or trend data. You can fork it on Parse and revise it to add a price-history endpoint if you need time-series data.How do I look up a skin slug if I only know the item name?+
list_skins with the item_filter parameter set to a partial item name (e.g. Assault Rifle). Each result includes a slug field you can pass directly to get_skin_details. Alternatively, search_items with a keyword returns mixed item and skin results, each with a slug and type to distinguish them.