Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rbxweb.net/llms.txt

Use this file to discover all available pages before exploring further.

The UGC Scanner lets an authenticated Discord user scan the Roblox catalog for items they sell — either under their own account or under a group they own — and export the result as a CSV. It’s available at Dashboard → UGC Scanner, in the same user-level menu group as Roblox Authorization. You don’t need a Discord server to use it.

Prerequisites

You must link at least one Roblox account via Roblox Authorization. If you haven’t, the UGC Scanner page shows a card pointing you there. The scanner reads from public Roblox endpoints, so you don’t grant the bot any special permission to your account — it only needs to know which Roblox account is “yours” so it can show you your groups.

Flow

1

Open UGC Scanner

Sidebar → UGC Scanner.
2

Pick a Roblox account

If you’ve linked multiple accounts, tabs at the top let you switch between them. Each account has its own scan history.
3

Refresh groups

Click Refresh groups the first time. The scanner fetches the list of groups you own and shows them as cards alongside your own profile.
4

Select a target

Click a card — your user (your own catalog) or any group you own. The selected card glows blue.
5

Start Scan

Click Start Scan. The status panel shows live progress (items scanned). A scan completes when the catalog cursor runs out of pages.
6

Generate CSV

Once a target has scanned items, an Existing Scans card appears with a per-target row. Click Generate CSV, pick which columns to include (ID / Name / Description are always included), and you get a 1-hour download link.

Targets

Each Roblox account shows two kinds of targets:
TypeWhat it scans
User (always present)Items sold under your own Roblox account
GroupItems sold by a group where your role’s rank is 255 (owner). One card per owned group.
If a group’s icon doesn’t appear, the bot’s batched icon fetch hit a transient error — try Refresh groups again.

Scan controls

  • Start Scan — enabled when a target is selected and no scan is currently running for your account.
  • Stop — enabled while a scan is pending, active, or stop_requested. Clicking stops the scan at the next page boundary; items scanned so far are kept.
  • Status panel — shows a spinner and the running item count while a scan is alive. The total isn’t known up front because Roblox’s catalog endpoint doesn’t return a total.
Scans run one at a time per bot process. If another user starts a scan while yours is queued, both run in order. This keeps each scan running at the full per-IP rate-limit budget against Roblox.

Scan credits

Every Discord user gets 3 free scans per week. Each scan costs 1 credit per selected target — scanning a group counts as 1 regardless of how many items inside, and scanning your own catalog is another 1. Credits refill weekly. The reset day is the same weekday you first authorized your Roblox account — so a user who authorized on a Wednesday refills every Wednesday, and a user who authorized on a Friday refills every Friday. Re-authorizing the same Roblox account, or adding a second / third / fourth Roblox account on the same Discord, does not reset the anchor — your first-ever auth date is what counts. Surplus carry-over: if you have unspent credits at the end of a week (from a future tier-up promotion, for example), they roll over. The refill never reduces an existing surplus — it only tops up if your remaining count is below the cap. Paid scans (top-ups) are reserved for a future feature and are currently not available. The dashboard shows a “Paid scans: 0 (currently not available)” row as a placeholder. Once paid scans ship, the deduction order will be free first, then paid — so you don’t accidentally burn through a paid top-up while you still have free credits sitting on the counter. Over-quota selection: if you select more targets than you can afford, the extra cards light up red and the Start button disables with a “Need N more credits” label. Deselect enough to fit your remaining count, or wait for the next refill.

CSV export

Click Generate CSV on an Existing Scans row to open the field-selection modal.
  • Required (always included): id, name, description. Greyed out and pre-checked — you can’t remove them.
  • Optional: price, lowestPrice, lowestResalePrice, favoriteCount, itemCreatedUtc, itemType, assetType, url, saleStatus, saleLocationType, lastScannedAt. All pre-checked; uncheck what you don’t want.
Excel-friendly tricks built in:
  • The CSV is written with a UTF-8 BOM, so emoji / Cyrillic / CJK render correctly (no 🥶 mojibake).
  • The id column is wrapped as ="<digits>", so Excel keeps it as text instead of converting long IDs to scientific notation (1.23E+13).
  • The url column is wrapped as =HYPERLINK(...), so URLs are clickable in Excel and Google Sheets.
After clicking Generate, the page shows a green download card. The link is valid for 1 hour. After that:
  • The link returns 410 Gone if you try to use it.
  • A background task on the bot deletes the file from disk so it doesn’t linger.
  • The cleanup also runs on bot startup, so even if the bot was offline the entire hour, the file is removed when it comes back up.
You can generate a new CSV (with different columns, for example) any time — every download has its own token and 1-hour window.

Delete data

The Delete data button on an Existing Scans row wipes all scanned items for that target. Use this if you re-scan and want a fully clean slate. It doesn’t affect any other target on the same Roblox account.

Limits & notes

  • Sales data is not in the public catalog. Per-item sales counts and revenue are visible only in your Roblox Creator Hub dashboard. The scanner shows you favorites count (a popular-item proxy) and resale floor price (for Limiteds), both of which are public.
  • Favorite counts come from the catalog response directly — no separate fan-out call, so a 10k-item scan completes in roughly the same wall-clock time whether or not you include the favorites column.
  • Anonymous calls only. The scanner uses Roblox’s public catalog endpoints with no auth, so its throughput is capped at the per-IP anonymous rate limit (community-empirical ~60 req/min). The scanner stays at 50 req/min to leave headroom.