Skip to main content
This guide walks you through everything you need to make a live CS2 item price request with the CS2Cap SDK. You’ll set up your credentials, send a request, read the response, and know how to handle the most common errors — all before you write a single line of production code.
1

Install the SDK

Install the SDK for the language you are using.
2

Set up environment variables

Store your base URL and API key as environment variables so you never hardcode credentials into your code.
Generate your API key from the Account page at cs2cap.com after verifying your email address.
3

Make your first request

Query the /prices endpoint for an AK-47 | Redline (Field-Tested) across the Steam marketplace. This is the fastest way to confirm your key is working and to see what a real response looks like.
4

Understand the response

The /prices response has three top-level fields:
  • items — the records you asked for, one object per provider result
  • meta — response context: the currency you requested, your filter parameters, and which providers actually returned data
  • pagination — paging state. Cursor endpoints such as /sales and /prices/history use next_cursor and report total: -1; do not treat that value as a record count.
The following illustrative response shows a separate Doppler query, not the AK-47 request above.
All price fields use minor units (integer cents). A lowest_ask of 2550 with currency: USD means $25.50. Divide by 100 to convert to the major unit for any two-decimal currency.
5

Common next requests

Once you have a working /prices call, these four requests cover the most frequent follow-up queries. The item_id lookup is a good second step — it gives you the stable numeric ID you can reuse across endpoints without passing the full item name each time.
Buy orders require Starter or higher. Sales and raw history require Pro or higher. If your tier does not include an endpoint, the request returns 403 until you upgrade. See Pricing & Plans for a full endpoint-by-tier breakdown.
6

Handle common failures

The table below covers the errors you’re most likely to encounter while integrating. Treat these as your first-line debugging checklist before opening a support ticket.
Do not retry 401 or 422 errors without first fixing the underlying issue — they will not self-resolve. For these read requests, retry transient 503 errors with bounded backoff and respect Retry-After on 429. Monthly quota exhaustion requires waiting for the reset or upgrading your plan.

Next steps

Authentication

Learn how API keys work and how to rotate them.

Core concepts

Understand providers, minor units, pagination, and the data model before you build.

API reference

Browse every endpoint: prices, bids, sales, analytics, portfolio, and account management.

Pricing & plans

Compare Free, Starter, Pro, and Quant tiers by endpoint access, rate limits, and monthly quotas.
Last modified on September 10, 2026