[Full Release] IsVerified API Now Supports Verification Levels
Key Takeaways
The IsVerified API now supports verification levels. You can require a Low or High verification threshold to gate features like trading or ranked matchmaking.
Pass either Enum.VerifiedLevel.Low or Enum.VerifiedLevel.High to the method.
Hi Creators,
Today, the IsVerified API now supports verification levels, giving you more granular control over how you gate features by a user’s verification status. We launched the IsVerified API beta three years ago to support user authenticity and deter repeat offenders in your games. During this extended beta period, we focused on improving accuracy and building a flexible architecture that can accommodate many different types of verification signals. As Roblox’s verification and security measures have evolved, this full release reflects those backend improvements while setting up support for additional verification methods in the future.
What’s New
You can now pass in either Enum.VerifiedLevel.Low or Enum.VerifiedLevel.High as an argument to the method. These indicate whether a user has passed a low or high threshold of verification according to Roblox.
This update is fully backwards-compatible. If you don’t provide a parameter, the method defaults to Low, so your current implementations keep working with no changes.
local Players = game:GetService("Players")
Players.PlayerAdded:Connect(function(player)
-- Usage 1: Default (No parameter passed - defaults to Enum.VerifiedLevel.Low)
local isDefaultVerified = player:IsVerified()
-- Usage 2: Explicit Low verification check
local isLowVerified = player:IsVerified(Enum.VerifiedLevel.Low)
-- Usage 3: Explicit High verification check
local isHighVerified = player:IsVerified(Enum.VerifiedLevel.High)
-- Implementation Example
if isHighVerified then
-- Grant access to high-stakes features (e.g., Ranked Matchmaking)
print(player.Name .. " meets the High…