Fandom APIvalorant.fandom.com ↗
Retrieve VALORANT cosmetic collection data from valorant.fandom.com: skin names, item types, weapons, editions, codenames, artwork URLs, and bundle pricing.
What is the Fandom API?
This API exposes VALORANT cosmetic collection data from valorant.fandom.com across 2 endpoints, covering roughly 117 collection pages including bundles and battle pass sets. The get_collection endpoint returns every item listed in a collection — weapon skins, melee skins, and accessories — alongside infobox metadata like edition tier, release patch, codename, and full-resolution artwork image URLs. The list_collections endpoint pages through the full catalog alphabetically.
curl -X GET 'https://api.parse.bot/scraper/de3ebee1-c3bc-4202-a6fb-c47c783791e0/list_collections?from_title=KTAC+Collection' \ -H 'X-API-Key: $PARSE_API_KEY'
Lists cosmetic collection pages from the wiki's Cosmetic Collections category, in the wiki's alphabetical order. One page of the category (up to 200 category members, of which only collection pages are returned, typically ~117) per call; when has_more is true, pass next_from as from_title on the next call to continue. Each entry's page_title is the exact value get_collection accepts.
| Param | Type | Description |
|---|---|---|
| from_title | string | Continuation token: the page title to start the listing from, taken unchanged from a previous response's next_from. Omitted = start of the category. |
{
"type": "object",
"fields": {
"count": "integer, number of collections on this page",
"has_more": "boolean, true when another page follows",
"next_from": "string continuation token for from_title, or null on the last page",
"collections": "array of {name, page_title}; page_title is the wiki page title to pass to get_collection"
},
"sample": {
"data": {
"count": 117,
"has_more": true,
"next_from": "KTAC Collection",
"collections": [
{
"name": ".EXE Collection",
"page_title": ".EXE Collection"
},
{
"name": "Kuronami Collection",
"page_title": "Kuronami Collection"
}
]
},
"status": "success"
}
}About the Fandom API
Endpoints Overview
The list_collections endpoint pages through the wiki's Cosmetic Collections category in alphabetical order. Each call returns up to ~117 collection entries, with each entry containing a name and page_title. When has_more is true, pass the next_from string back as the from_title parameter to fetch the next page. This makes it straightforward to crawl the full catalog incrementally.
Collection Detail
The get_collection endpoint accepts a collection parameter (the wiki page title, with spaces or underscores). It returns the collection's name, edition (e.g. Exclusive, Premium, Select), codename, release_patch, battle_pass_act, cosmetic_types, page_url, and item_count. For battle pass collections, release_patch is null and battle_pass_act is populated; the reverse holds for store bundles.
Items Array
The items array within a get_collection response lists every cosmetic in page order. Each item carries name, item_type (Weapon Skin, Melee, or an accessory type), source, bundle, weapon (the base weapon name for Weapon Skin items), and battle_pass_tier (an integer for battle pass items, null otherwise). This structure makes it possible to filter by item type or weapon without additional parsing.
Coverage Notes
Data reflects what the wiki community has published for each collection page. Infobox fields like codename or bundle price text may be null on pages where the wiki has not populated them. Image URLs resolve to full-resolution artwork hosted on the fandom CDN and can be used directly in applications.
The Fandom API is a managed, monitored endpoint for valorant.fandom.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when valorant.fandom.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 valorant.fandom.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 searchable VALORANT skin database filtered by weapon type using the
weaponfield fromget_collection. - Track which collection a specific skin belongs to by iterating
list_collectionsand matching item names. - Display bundle artwork in a companion app using the full-resolution image URLs returned by
get_collection. - Identify all battle pass cosmetics by checking
battle_pass_actandbattle_pass_tierfields. - Catalog edition tiers (Exclusive, Premium, Select) across the full collection catalog for pricing analysis.
- Audit internal codenames across all collections by pulling the
codenamefield from eachget_collectionresponse. - Enumerate all melee skins in the game by filtering
itemswhereitem_typeequals 'Melee'.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does valorant.fandom.com have an official developer API?+
What does get_collection return for a battle pass collection versus a store bundle?+
release_patch is populated and battle_pass_act is null. For battle pass collections, battle_pass_act is populated and release_patch is null. Individual items in battle pass collections also carry a battle_pass_tier integer indicating their tier position.How does pagination work in list_collections?+
has_more is true, a next_from string is included. Pass that value as the from_title parameter in your next call to continue. When has_more is false and next_from is null, you have reached the end of the catalog.Does the API return individual skin variant or level data (e.g. finisher animations, skin levels, variant colors)?+
Are skin prices or VP costs returned by the API?+
items array. This reflects what the collection page itself exposes. You can fork this API on Parse and revise it to pull pricing from dedicated skin pages if those fields are available there.