Roblox Limited Item Price Scraper avatar

Roblox Limited Item Price Scraper

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Roblox Limited Item Price Scraper

Roblox Limited Item Price Scraper

Tracks resale prices, recent average prices, and market data for Roblox Limited items using the public Roblox Economy API. No proxies or login required.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

COSENT GROUP

COSENT GROUP

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Share

Pull real-time market data for Roblox Limited items using the public Roblox Economy API. No Roblox account, no proxies, and no browser automation required — this actor makes direct API calls and returns clean, structured data.

What it returns

  • Recent Average Price (RAP) — the rolling average of recent resale transactions. The standard valuation metric used by the trading community.
  • Lowest Ask — the current cheapest listing available to buy right now.
  • ROI — how much the item has appreciated since its original sale price (e.g. 101,701% means the item is worth 1,017× what it originally cost).
  • Market Cap — RAP × total quantity in existence. Shows the total Robux value locked in all copies of an item.
  • Value Category — Classic Limited (original Roblox-issued items with full RAP history) or UGC Limited (newer creator-made items).

Results are sorted by RAP descending — the highest-value items appear first in your dataset.

How to find items

You have two ways to specify which items to look up:

  1. Asset IDs — paste asset IDs directly. Find an item's ID in the URL on the Roblox catalog: roblox.com/catalog/21070012/... → ID is 21070012.
  2. Search Keywords — enter terms like dominus, sparkle time, or red fedora. Each keyword is searched independently and returns up to 30 results per page (increase with Max Pages Per Keyword).

Classic vs. UGC Limiteds

Roblox has two categories of Limited items:

  • Classic Limiteds — original items issued directly by Roblox, with small fixed quantities and decades of trade history. These carry RAP, ROI, and market cap data. Examples: Dominus Empyreus, Sparkle Time Fedora, Korblox Deathspeaker.
  • UGC Limiteds — newer creator-made items. Larger supplies, lower prices, no RAP history. Enable Classic Limiteds Only to exclude these.

Example output

{
"assetId": "21070012",
"name": "Dominus Empyreus",
"valueCategory": "Classic Limited",
"isLimited": "true",
"isLimitedUnique": "false",
"totalQuantity": "13",
"originalPrice": "13337",
"recentAveragePrice": "13577229",
"lowestResalePrice": "618033988",
"totalSales": "108",
"roi": "101701%",
"marketCap": "176503977",
"creatorName": "Roblox",
"assetType": "Hat",
"createdAt": "2010-02-09T00:00:00Z",
"catalogUrl": "https://www.roblox.com/catalog/21070012",
"scrapedAt": "2026-08-01T00:03:12.702Z"
}

Input fields

FieldTypeDefaultDescription
assetIdsarrayRoblox asset IDs to look up directly.
keywordsarraySearch terms — each searched separately, up to 30 results/page.
maxPagesPerKeywordinteger1Pages of catalog results per keyword (30 items/page, max 5).
classicOnlybooleanfalseSkip UGC Limiteds; return only original Classic Limited items.
maxItemsinteger0Cap total results returned (0 = no limit).
includeNonLimitedbooleanfalseReturn data for non-Limited items (useful for debugging IDs).

Tips for traders

  • Compare Lowest Ask vs. RAP: when the lowest ask is significantly below RAP, the item may be underpriced relative to market consensus.
  • Market Cap helps you gauge liquidity: a small-quantity item with high RAP will have a very different market character than one with thousands of copies.
  • Schedule this actor to run daily and compare results over time to track which items are appreciating.
  • Use Max Pages Per Keyword set to 3–5 to pull a wider catalog view when scanning an entire category.

Rate limits & fair use

This actor uses the public Roblox Economy API with a 300ms delay between requests. Roblox does not publish official rate limits for these endpoints. Running large batches (500+ items) is generally fine; avoid running multiple concurrent instances against the same endpoints.