How We Verify Every ID

The problem we're solving

Since Roblox's 2022 audio-privacy change, most music-code lists on the internet are largely dead — uploads get deleted, moderated or made private, and static lists never notice. Sites listing “5,000 working codes” typically haven't checked them in years. We built rblxdb around one rule: never show an ID we haven't recently checked.

The method

1. The source of truth — every audio ID is checked against Roblox's own economy API. An audio asset is playable by everyone only when Roblox marks it public-domain; that flag, not guesswork, decides the badge.
2. Rolling re-checks, around the clock — an automated job re-verifies IDs continuously, oldest-checked first, so every published song cycles through verification perpetually.
3. Two strikes before “Not Working” — Roblox's APIs occasionally return transient wrong answers, so one failed check never flips a badge. Two consecutive failures do.
4. Reports jump the queue — every song page has a “Not working? Report it” button. Reported IDs are re-checked within the hour, ahead of everything else.
5. Timestamps are public — every song page and every API response carries verifiedAt, the exact time of the last check, and status-change history where we have it. The badge on a song, decal or item page opens: click it and it shows what was read, when, and against which source. You never have to take our word for it.

How game codes are verified

Codes work differently from IDs. Roblox has no API that can test one, so no machine anywhere — ours included — can redeem SUMMER2026 and see what happens. What we can do is read the game's own published code list every six hours, and count what players tell us after they try one.

Because those two signals are not equally strong, codes do not all get the same badge. Every code carries the strongest claim its own evidence supports, and no more. That claim is computed from stored evidence, not written by hand, so the badge, the page text and the structured data cannot drift apart.

The seven things a code badge can say

• Verified working — the code is in the game's own published list, and we re-read that list within the last 24 hours and found it still there. This is the only badge backed by a check we performed ourselves.
• Developer listed — the game publishes this code itself, but our last successful read of its list is older than 24 hours. The provenance is good; the freshness is not, so we drop the claim rather than let a broken job keep asserting it.
• Community confirmed — at least 3 players voted and most of them redeemed it successfully. Nothing our pipeline does is stronger than this, because it is the only evidence that involves the code actually being typed into the game.
• Likely working — someone reported it worked, but not enough people to settle it and not from a source we can re-read. Worth trying, not worth trusting.
• Unconfirmed — it came from a public list and this game doesn't publish its codes anywhere we can read. We have never verified it and neither has anyone else who told us. Most competing sites badge codes like this as working; that is the badge this ladder exists to refuse.
• Likely expired — 3 or more players voted and most of them could not redeem it. Player verdicts outrank our own provenance, so a code the game still lists can still be marked this way.
• Expired — it has dropped out of the game's list. We keep it visible instead of deleting it, so you can tell a code that has been retired from one that was never real.

One vote never moves a badge: a verdict needs 3 players before it outranks anything, so a single annoyed voter cannot expire a working code. Those verdicts are also what the contributor leaderboard scores — a verdict counts once the pipeline later agrees with it, so points measure being right, not being busy.

What we can't verify

This is the part most methodology pages leave out, so here it is plainly. Our code check reads one thing: the game's own description, where a developer publishes their live codes. That is a genuine re-check, and it is also a narrow one — 13% of the 3,597 live codes we list come from a description we can read. For the other 87%, the game publishes its codes somewhere we have no access to — a Discord announcement, a video, an in-game notice — and no amount of crawling on our side changes that.

Those codes are not verified by us. They can only be confirmed by a player redeeming one and telling us, which is exactly why the Worked / Didn't buttons exist and why a handful of player votes outranks our own pipeline on this page. Until those votes arrive, the code sits at Unconfirmed and we say so on the badge rather than rounding it up to working.

Two further limits worth naming. Redeeming a code takes a real Roblox account, so promo codes and star codes cannot be machine-checked at all — those are editorially cross-checked against multiple independent sources and stamped with the check date, which is weaker evidence and is labelled as such. And a code we verified an hour ago can be pulled by the developer five minutes later; a timestamp is a record of when we looked, not a guarantee about now. That is why each badge shows the time of the check next to it — so you can judge how much it is worth instead of taking our word for it.

Use the data

The verification results are free to build on: the rblxdb API serves every ID with its isWorking flag and timestamp — no key required. If you run a site or tool that lists Roblox codes, cite or consume the feed instead of testing manually. Questions about the methodology: ads@rblxdb.com.