Skip to main content
Every CS2Cap endpoint returns a predictable set of fields. This reference covers what each field means, its type, which endpoints return it, and any important formatting rules you need to follow when reading values — especially the minor-units convention for all price data.
All price fields (lowest_ask, highest_bid, price, best_ask, item_value, total_value) are returned in minor units of the response currency. Divide by 100 to get the display value. For example, lowest_ask = 2550 with currency = USD means $25.50.
/prices and /bids also return a string companion to the integer price — lowest_ask_decimal and highest_bid_decimal. These carry adaptive precision: two decimal places at or above 1.0, eight below it. Use them for low-value currencies (notably crypto such as BTC) where the integer minor-units field rounds to 0. For example, a $25.50 skin priced in BTC returns lowest_ask = 0 but lowest_ask_decimal = "0.00041600".

Field availability

Fields marked Yes are included in that endpoint’s response. Fields marked are not.

Portfolio and transaction fields

These fields are specific to the portfolio system and appear on /portfolio/items and /portfolio/transactions.

Item identity

These fields identify an item and appear in most responses across the API.

Price fields

All price fields are returned in minor units of the response currency. See the note at the top of this page.

Sale fields

Timestamp fields

Pagination

List endpoints return a pagination object alongside items.
On cursor-based endpoints, pagination.total is always -1. Use has_next and next_cursor to paginate.

Response envelope

Most list endpoints return these top-level fields:

Item catalog fields

These fields are returned by /items.
Last modified on July 12, 2026