We will not provide an alternative for the voicesettings endpoint as overriding voice chat settings for specific private servers is no longer a first-party feature offered by Roblox.
Please let us know via private message if you have any questions or concerns.
We are planning to remove the following API endpoint on November 11, 2025. This endpoint returns information about experiences created by a given user. If you are using this endpoint please switch to the newer endpoint as recommended below, which provides the same functionality:
Old API: https://www.roblox.com/users/profile/playergames-json
New API: https://games.roblox.com/v2/users/userId/games
You can find documentation for the new API endpoint here:
We are making a change so that the Roblox game client enforces users inventory privacy settings going forward. This involves a change in behavior of PlayerOwnsAsset, starting January 27th, 2026.
Today, this method can be used on the client side (via LocalScript) to check if another player owns an asset. For now, no changes will be made for calls originating on the server. But for calls being made from a LocalScript, if the call is made for one player checking another player’s inventory, the inventory privacy setting will take effect next month, and the method will throw an error.
If this is important to your experience, please make sure your experience is calling PlayerOwnsAsset on the server by January 27th, 2026.
For now, this change only applies to assets, but we may explore and announce similar changes for other inventory item types in the future in order to enhance privacy on Roblox.
This change also applies to all web endpoints exposed via inventory.roblox.com (v1, and v2). If you are consuming the web APIs directly, please use our Open Cloud Inventory endpoints which support API keys and OAuth.
We are making changes to ensure that access to badge ownership information more consistently respects players’ privacy. These changes affect both engine BadgeService methods and badges web APIs, and will begin rolling out on March 23rd, 2026.
At a high level:
If your experience uses BadgeService to check badges from your own experience, the behavior should remain the same.
If your experience uses BadgeService to check badges from other experiences only for players that are (or have recently been) in the server, the behavior should remain the same.
If you are using UserHasBadgeAsync or CheckUserBadgesAsync to check badge ownership of badges from other experiences for users who have not recently been in the server, those checks will stop returning information after this change.
For more details, check out the full DevForum post here.
We are deprecating the productId field for Creator Store asset types. This change ensures that the assetId is the single identifier for Store items. This change will be made on March 30th, 2026.
This change applies to the following Creator Store asset types:
Models
Audio
Plugins
Decals
MeshParts
Video
Fonts
The productId field will no longer be set for these asset types. When calling MarketplaceService:GetProductInfo or using web APIs, the productId will now return 0.
This update applies to both new and existing assets within the categories listed above. ProductId is not used for creator store asset types, however, if you rely on them in script for any reason, they will be set to return 0 moving forward for these asset types.
Please let us know if you have any questions or concerns. Thank you.
For instructions on how to upload models, meshes, and animations through the Open Cloud API, follow our usage guide.
These changes will go into effect on April 13th, 2026. Please migrate any workflows from these legacy endpoints to Open Cloud to avoid disruption. For more details, see the original DevForum announcement here.
We will be removing the following Economy API endpoint on April 10, 2026: https://economy.roblox.com/v1/purchases/products/{productId}
This endpoint is part of an older, legacy purchase flow that is no longer supported.
If you are currently relying on this endpoint, please plan to migrate to the in-experience purchasing APIs (for example, MarketplaceService purchase flows within your experience) instead.
We will be deprecating a set of legacy game pass and developer product APIs on April 23, 2026. These endpoints are part of older management flows that have been superseded by newer Open Cloud APIs for game passes and developer products. Please review the list below and plan your migration before that date.
Affected endpoints
The following legacy game pass management endpoints will be deprecated:
POST https://apis.roblox.com/game-passes/v1/game-passes/universes/{universeId}/products-by-ids/creator
GET https://apis.roblox.com/game-passes/v1/game-passes/universes/{universeId}/creator
POST https://apis.roblox.com/game-passes/v1/game-passes/{gamePassId}/details
POST https://apis.roblox.com/game-passes/v1/game-passes
GET https://apis.roblox.com/game-passes/v1/game-passes/{gamePassId}/regional-pricing/preview
The following legacy developer product management endpoints will be deprecated:
POST https://apis.roblox.com/developer-products/v1/developer-products/{productId}/image
GET https://apis.roblox.com/developer-products/v1/developer-products/{productId}/creator-details
POST https://apis.roblox.com/developer-products/v1/universes/{universeId}/developerproducts
POST https://apis.roblox.com/developer-products/v1/universes/{universeId}/developerproducts/{productId}/update
GET https://apis.roblox.com/developer-products/v2/developer-products/universes/{universeId}/creator
GET https://apis.roblox.com/developer-products/v1/developer-products/{developerProductId}
GET https://apis.roblox.com/developer-products/v1/universes/{universeId}/regional-pricing/preview
Recommended alternatives
Going forward, please use the following Open Cloud APIs to manage game passes and developer products:
These Open Cloud endpoints support API key, OAuth 2.0, and cookie-based authentication and are the recommended way to programmatically manage your products going forward.
We will be removing the field priority from group roles in this endpoint entirely after May 28:
GET groups.roblox.com/v2/groups/{groupId}/users
This field doesn’t have any meaningful information. It’s just the index of the element in the roles list, so we’re removing it to streamline the endpoint response.
Please update your code not to depend on this field being present in the response.
We will be deprecating Regional Pricing fields from the Public Web APIs for developer products and game passes effective July 20, 2026. This field will be removed from the create and update endpoints for both developer products and game passes.
We will also be deprecating the storePageEnabled field from the developer products APIs. Going forward, Shop will replace storePageEnabled for developer product listing status.
Affected endpoints:
Today, setting isRegionalPricingEnabled will also update Managed Pricing for that item. After July 20, 2026, please do not send isRegionalPricingEnabled in requests to the following public endpoints:
After July 20, 2026, storePageEnabled will be deprecated across the following developer product public endpoints. Please do not send it in write requests, and it will no longer be returned by read endpoints:
Going forward, integrations should rely on Managed Pricing behavior via isManagedPricingEnabled. For developer product listing status, integrations should rely on Shops.
This should be entirely backwards compatible with Regional Pricing and can be treated as such.
We no longer plan to update the scope sets of the original routes. In general, we recommend you to view Scopes | Documentation - Roblox Creator Hub instead of directly hitting any of these endpoints. Please let us know if you have any questions or concerns. Thank you.
