Playvalorant APIwiki.playvalorant.com ↗
Access VALORANT weapon skin data from wiki.playvalorant.com: skin names, weapons, editions, VP costs, bundle images, and full collection details via 3 endpoints.
What is the Playvalorant API?
The VALORANT Wiki Skins API exposes weapon skin and bundle collection data from wiki.playvalorant.com across 3 endpoints. Use list_store_skins to page through every skin row in the wiki's in-game store table — including skin name, weapon type, edition tier, VP cost, and parent collection — or use get_collection to pull a single bundle's artwork URL, infobox details, and per-skin costs. Coverage includes all store collections and VCT team capsules.
curl -X GET 'https://api.parse.bot/scraper/d49f35e6-beb7-487b-9b77-fba0c295eae4/list_store_skins?weapon=Vandal' \ -H 'X-API-Key: $PARSE_API_KEY'
Lists every weapon skin in the VALORANT Wiki's in-game store table (all store collections plus the VCT team capsules), one row per skin, in the wiki's order (collections alphabetically). Each row carries the skin name, weapon, parent collection with its wiki page slug (collection_slug, the input for get_collection, which supplies the bundle image), edition tier, cost in VALORANT Points (integer VP, null when the wiki lists no price), the full-resolution skin image URL and the edition icon URL. limited_time marks collections the wiki flags as limited-time (cannot appear in daily offers); bundle_only_price marks skins whose stated price was only available as part of the full bundle. Optional filters are applied locally after the whole table is loaded in a single request: weapon and edition are exact case-insensitive matches, collection is a case-insensitive substring match; an unrecognised filter value yields an empty page. Paging is a true offset over the filtered list: offset (default 0) and limit (default 100, max 1000); total_matched is the filtered count, total_on_site is the whole table (845 rows at build time), has_more tells whether another page exists.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum skins returned per call; values above 1000 are clamped to 1000. |
| offset | integer | Number of matching skins to skip before the returned page. |
| weapon | string | Exact weapon name as shown on the wiki (one shape: Vandal). Melee skins have weapon Melee. Omitted = all weapons. |
| edition | string | Edition tier as labelled on the wiki (values seen this build: Select, Deluxe, Premium, Exclusive, Ultra). Omitted = all editions. |
| collection | string | Case-insensitive substring matched against the collection name (e.g. abyss matches Abyssal). Omitted = all collections. |
{
"type": "object",
"fields": {
"count": "number of skins in this page",
"limit": "limit applied after clamping",
"skins": "array of skin rows: skin_name, weapon, collection, collection_slug (input for get_collection), edition, cost (integer VP or null), cost_currency, bundle_only_price (boolean), limited_time (boolean), skin_image (URL), edition_icon (URL)",
"offset": "offset applied",
"has_more": "true when offset + count < total_matched",
"total_matched": "number of skins matching the filters across the whole table",
"total_on_site": "number of skin rows in the wiki table before filtering"
},
"sample": {
"data": {
"count": 1,
"limit": 1,
"skins": [
{
"cost": 1275,
"weapon": "Sheriff",
"edition": "Deluxe",
"skin_name": "Abyssal Sheriff",
"collection": "Abyssal",
"skin_image": "https://wiki.playvalorant.com/en-us/images/Abyssal_Sheriff.png",
"edition_icon": "https://wiki.playvalorant.com/en-us/images/Deluxe-edition-icon.png",
"limited_time": false,
"cost_currency": "VP",
"collection_slug": "Abyssal_Collection",
"bundle_only_price": false
}
],
"offset": 1,
"has_more": true,
"total_matched": 845,
"total_on_site": 845
},
"status": "success"
}
}About the Playvalorant API
Endpoints and Data Shape
list_store_skins returns a paginated list of every weapon skin in the wiki's store table, one object per skin. Each row includes skin_name, weapon, collection, collection_slug, edition, cost (integer VP or null), and a skin_image URL. Filter by exact weapon name (e.g. Vandal, Melee), edition tier (Select, Deluxe, Premium, Exclusive, Ultra), or a case-insensitive substring on collection. The response also exposes total_matched and total_on_site so you can track pagination state with has_more, offset, and limit (clamped to 1000).
Collection Detail
get_collection accepts a collection_slug — returned as collection_slug in any list_store_skins row — and returns the full bundle record for that collection: bundle_image (full-resolution artwork URL from the wiki infobox), bundle_cost (integer VP for the full bundle or null), edition, skin_count, and a skins array with per-skin cost, skin_image, and weapon. The details object carries all raw infobox label-value pairs for that collection page.
Bulk Collection Listing
list_collections returns the same bundle record structure as get_collection for every collection in the store table in one call, paginated with a 500-per-page cap. Each entry includes collection_slug, collection, page_title, bundle_image, edition, and bundle_cost. The response includes a pages_not_found array listing any slugs whose wiki page could not be resolved — useful for detecting stale references. At the time this API was built, 183 collections were tracked.
The Playvalorant API is a managed, monitored endpoint for wiki.playvalorant.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wiki.playvalorant.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.playvalorant.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 VALORANT skin price tracker that filters by edition tier and displays current VP costs from the wiki.
- Generate a visual skin catalog app using bundle artwork URLs from bundle_image and per-skin skin_image fields.
- Compare bundle cost vs. individual skin costs across collections using bundle_cost and per-skin cost fields.
- Enumerate all Melee skins across every collection by filtering list_store_skins with weapon set to Melee.
- Sync a game database with the full collection roster using list_collections in a single paginated call.
- Display VCT team capsule offerings alongside standard store collections using the unified list_store_skins endpoint.
- Identify which collections belong to a specific edition tier (e.g. Ultra) by filtering on the edition parameter.
| 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.