clientsettings.roblox.com APIclientsettings.roblox.com ↗
Retrieve Roblox client version, feature flags, and user channel assignment via the clientsettings.roblox.com API. 3 endpoints covering WindowsPlayer, MacPlayer, and more.
curl -X GET 'https://api.parse.bot/scraper/414d6537-18d9-47af-878c-761accbc229a/get_client_version' \ -H 'X-API-Key: $PARSE_API_KEY'
Get the current client version, version upload hash, and bootstrapper version for a specific Roblox binary type and channel.
| Param | Type | Description |
|---|---|---|
| channel | string | The deployment channel name (e.g. LIVE). Non-LIVE channels may require authorization. |
| binary_type | string | The Roblox binary type. Accepts exactly one of: WindowsPlayer, MacPlayer, WindowsStudio64, MacStudio. |
{
"type": "object",
"fields": {
"version": "string - semantic version (e.g. 0.723.0.7230785)",
"bootstrapperVersion": "string - bootstrapper version string",
"clientVersionUpload": "string - version upload identifier hash"
},
"sample": {
"version": "0.723.0.7230785",
"bootstrapperVersion": "1, 6, 0, 7230785",
"clientVersionUpload": "version-460909c4fe904aae"
}
}About the clientsettings.roblox.com API
This API exposes 3 endpoints covering Roblox client versioning, application feature flags, and channel assignment directly from clientsettings.roblox.com. The get_client_version endpoint returns the current semantic version, bootstrapper version, and upload hash for binary types including WindowsPlayer, MacPlayer, WindowsStudio64, and MacStudio. The get_application_settings endpoint returns the full set of active feature flags as key-value pairs, while get_user_channel identifies the assigned deployment channel.
Client Version Data
The get_client_version endpoint accepts two optional parameters: binary_type (one of WindowsPlayer, MacPlayer, WindowsStudio64, MacStudio) and channel (e.g. LIVE). It returns three fields: version (a semantic version string like 0.723.0.7230785), bootstrapperVersion, and clientVersionUpload (a hash identifier tied to that release). Non-LIVE channels may require authorization and will return errors for unauthenticated requests.
Application Feature Flags
The get_application_settings endpoint accepts an application_name parameter — valid values include PCDesktopClient, PCStudioApp, MacDesktopClient, and MacStudioApp. The response is a single applicationSettings object: a flat dictionary mapping setting names to string values. This dictionary can be large, covering active feature flags, configuration toggles, and experiment parameters for the specified application at the time of the request.
Channel Assignment
The get_user_channel endpoint takes no inputs and returns a single channelName field. For unauthenticated requests this is typically LIVE. Channel assignment drives which version and feature set a given client receives, so this endpoint is useful for confirming the baseline channel before querying version or settings data.
- Detect the latest Roblox Windows or Mac client version to automate update checks in launcher tools
- Monitor changes to feature flags returned by get_application_settings across deployments
- Track the bootstrapperVersion field to identify when Roblox ships a new installer build
- Confirm the clientVersionUpload hash to verify which build artifact corresponds to a given release
- Check channelName from get_user_channel to determine baseline deployment context before querying other endpoints
- Diff applicationSettings responses over time to observe feature flag changes between client releases
- Identify when experimental flags are promoted to default by comparing PCDesktopClient vs PCStudioApp settings
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.