THE QUICK ANSWER
An out-of-stock record can contain old sale statistics and a suggested price. Those fields do not create an offer you can buy or a buyer for your item.
01
Separate no current stock from no historical record
Skinport documents a public out-of-stock dataset with suggested price, average sale price and sales count over the last ninety days. An item can therefore have past transaction evidence while no current listing is available.
This says nothing by itself about total supply in Steam inventories. Treat out of stock as the platform dataset’s current availability condition, not an economy-wide scarcity count.
Explanation: history can exist without an offer
Past sales
Historical average and ninety-day count.
Suggested amount
Reference, not an executable quote.
Current stock
Check an actual available listing separately.
Explanation diagram, not a website screenshot. No real item prices or scarcity claim.
Original explanation · not an account screenshot02
Read the three amounts and counts by their purpose
A suggested price is a reference, average sale price summarizes past completed transactions, and sales_last_90d counts observations in that period. Keep the named field attached to the value instead of calling every number the price.
For an invented row with reference 500, historical average 410 and two sales, the record does not offer two available items at 410. It describes a reference and a sparse historical sample.
| Fictional suggested price | 500 units; reference only |
|---|---|
| Fictional average sale price | 410 units; historical summary |
| Fictional sales_last_90d | 2 completed observations in the window |
| Available listing | Not established by those fields |
03
Keep the version with the market name
The official example uses a version field to distinguish Emerald within a broader Gamma Doppler item name. Retain that distinction when comparing records. Dropping version can mix a special variant into a different reference set.
If version is null, keep it null rather than inventing a phase or treating it as a numeric zero. Use the actual item’s inspect details when a precise phase or pattern is essential.
Explanation: an out-of-stock row needs context
Identity
Full name plus version.
Sample
Ninety-day sales count.
Freshness
One-hour documented cache.
Limit
No proof of worldwide supply or future value.
Explanation diagram, not a website screenshot. Original reading aid, not a reproduced API response.
Original explanation · not an account screenshot04
Respect the dataset’s longer cache
The out-of-stock endpoint is documented as cached for an hour. It should not be treated as an immediate reservation or stock alert. Check the actual Market item page for an available offer before relying on an old response.
Save retrieval time and source along with any comparison. A repeated cached row is not evidence that nobody listed or purchased an item during the interval.
05
Write a bounded availability statement
A useful note says the named Skinport record was out of stock at a stated observation time and had a particular historical sample window. Avoid statements that the item is unobtainable everywhere or certain to rise.
If you are researching a sale, the next step is an actual current quote or comparable offer—not multiplying the historical average by a claimed inventory count.
BEFORE YOU CONTINUE
Quick checklist
- Separate historical evidence from current availability.
- Keep suggested and average sale prices labelled.
- Preserve the version field.
- Record the one-hour cache and observation time.
Official sources
Official public documentation reviewed on 26 October 2026 (America/Toronto).
- Skinport REST API — Out of Stock · reviewed
Public documentation review only. No account was signed in, no order or trade was created, and no payment was made. Examples use invented amounts and do not report current market prices.
