Discover/Skinport API
live

Skinport APIskinport.com ↗

Access Skinport CS2 skin listings, item details, sales history, and aggregated pricing via 4 endpoints. Filter by category, exterior, and sort by price or date.

Endpoint health
verified 5d ago
get_price_list
get_sales_history
get_market_items
get_item_details
4/4 passing latest checkself-healing
Endpoints
4
Updated
1mo ago

What is the Skinport API?

The Skinport API provides access to CS2 skin marketplace data across 4 endpoints, covering live market listings, per-listing details, aggregated sales statistics, and a full catalog price list. The get_market_items endpoint lets you search and filter active listings by category, exterior condition, and keyword, returning structured records with sale IDs, prices, and wear data ready for downstream use.

This call costs1 credit / call— charged only on success
Try it
Number of items to skip for pagination.
Sort field for results.
Sort direction for results.
Free-text search query to filter items by name.
Category filter for item type.
Exterior condition filter.
→ api.parse.bot/scraper/978fc4bf-bc5a-4c23-b652-804404dcdcdb/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/978fc4bf-bc5a-4c23-b652-804404dcdcdb/get_market_items?skip=0&sort=date&order=asc&category=Knife&exterior=Factory+New' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 4 totalmissing one? ·

Browse the Skinport marketplace for CS2 item listings. Supports filtering by category, exterior condition, and free-text search. Results are paginated via skip offset and sortable by date or price. Returns up to 60 items per page plus filter metadata (total count, available exterior/other filters).

Input
ParamTypeDescription
skipintegerNumber of items to skip for pagination.
sortstringSort field for results.
orderstringSort direction for results.
querystringFree-text search query to filter items by name.
categorystringCategory filter for item type.
exteriorstringExterior condition filter.
Response
{
  "type": "object",
  "fields": {
    "meta": "object containing SEO content, description, and category info for the current filter",
    "items": "array of market listing objects with productId, url, marketName, salePrice, wear, category, exterior, etc.",
    "filter": "object containing total count and available filter options (components array)",
    "success": "boolean indicating whether the request succeeded",
    "requestId": "string unique request identifier"
  },
  "sample": {
    "data": {
      "items": [
        {
          "url": "talon-knife-doppler-factory-new+phase-2",
          "name": "Doppler",
          "wear": 0.0145,
          "title": "Talon Knife",
          "family": "Doppler",
          "rarity": "Covert",
          "saleId": 82547399,
          "shortId": "AJWJJKFDDA7",
          "category": "Knife",
          "currency": "USD",
          "exterior": "Factory New",
          "souvenir": false,
          "stattrak": false,
          "salePrice": 98115,
          "marketName": "★ Talon Knife | Doppler (Factory New)",
          "subCategory": "Talon Knife",
          "marketHashName": "★ Talon Knife | Doppler (Factory New)",
          "suggestedPrice": 89940
        }
      ],
      "filter": {
        "total": 3638094,
        "components": [
          {
            "data": [],
            "name": "price",
            "type": "priceBar",
            "appid": -1,
            "resolved": []
          }
        ]
      },
      "message": null,
      "success": true,
      "requestId": "f52985bb-99f0-674f-9e8b-87a22d136bbc"
    },
    "status": "success"
  }
}

About the Skinport API

Market Listings and Item Details

get_market_items returns paginated listing objects from the Skinport marketplace. Each record includes fields like saleId, url, marketName, salePrice, wear, category, and exterior. You can narrow results with the query parameter for keyword search, category for weapon type (Knife, Rifle, Gloves, Pistol, SMG, Heavy, Agent, Charm), and exterior for condition (Factory New through Battle-Scarred). Results are sortable by date or price in either direction using the sort and order parameters, with skip for pagination. The response also includes a filter object containing the total listing count and available filter facets.

get_item_details requires both a sale_id and a matching item_slug — the two must refer to the same listing or the request returns a not-found error. When matched correctly, the data object in the response includes the full item record with seller information, a list of similarItems, otherSales of the same item, trend data, sales history suitable for charting, a rating, offers, and a relatedItem object. This makes it useful for building per-listing detail pages or comparisons.

Sales History and Price List

get_sales_history accepts a market_hash_name such as AK-47 | Redline (Field-Tested) and returns price and volume statistics across four time windows: last_24_hours, last_7_days, last_30_days, and last_90_days. Each window exposes min, max, avg, median, and volume values, along with direct links via item_page and market_page fields.

get_price_list returns the full Skinport item catalog with current pricing metadata. Each record includes min_price, max_price, mean_price, median_price, quantity, and Unix timestamps for created_at and updated_at. You can request prices in a specific currency via the currency parameter and restrict results to tradable items only with the tradable boolean flag. This endpoint is suited for bulk price comparison and catalog indexing tasks.

Reliability & maintenanceVerified

The Skinport API is a managed, monitored endpoint for skinport.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when skinport.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 skinport.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.

Last verified
5d ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Track price trends for specific CS2 skins using 24h, 7d, 30d, and 90d statistics from get_sales_history
  • Build a skin deal-finder by filtering get_market_items by exterior and sorting by price ascending
  • Monitor new listings for a specific item type by querying get_market_items with a keyword and sorting by date
  • Compare seller offers and similar listings for a specific sale using get_item_details' similarItems and otherSales fields
  • Index the full Skinport catalog with min/max/median pricing using get_price_list for bulk price comparison
  • Filter tradable-only items from the price list using the tradable parameter for trade-bot pricing feeds
  • Compute market spread or volatility for an item by combining get_price_list mean/median with get_sales_history volume data
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 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.

Frequently asked questions
Does Skinport have an official developer API?+
Yes. Skinport provides a public API documented at https://docs.skinport.com. The Parse API covers the same marketplace data and adds search and per-listing detail endpoints that go beyond what the official API exposes.
What does get_item_details return beyond basic listing data?+
It returns a data object containing the full item record with seller info, a similarItems array, an otherSales list for the same item, trends, a history array suitable for charting price over time, a rating, offers, and a relatedItem object. Both sale_id and item_slug are required and must match the same listing.
Does get_sales_history return individual transaction records?+
No — it returns aggregated statistics only: min, max, avg, median, and volume for each of the four time windows (last_24_hours, last_7_days, last_30_days, last_90_days). Individual trade-level records are not exposed. You can fork this API on Parse and revise it to add a custom endpoint if your use case requires finer-grained transaction data.
Can I retrieve a seller's full listing history or profile data?+
Not currently. The API exposes seller information as part of individual item listings via get_item_details, but there is no endpoint for querying by seller or retrieving a seller's complete history. You can fork this API on Parse and revise it to add a seller-focused endpoint.
How does pagination work in get_market_items?+
Pagination uses an offset-based skip parameter — pass the number of items already retrieved to fetch the next page. The filter object in the response includes a total count, which you can use to determine when all results have been fetched.
Page content last updated . Spec covers 4 endpoints from skinport.com.
Related APIs in MarketplaceSee all →