Roblox 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.
What is the Roblox 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.
curl -X GET 'https://api.parse.bot/scraper/414d6537-18d9-47af-878c-761accbc229a/get_client_version?channel=LIVE&binary_type=WindowsPlayer' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace clientsettings-roblox-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.roblox_client_settings_api import RobloxClientSettings, BinaryType, ApplicationName
client = RobloxClientSettings()
# Get current client version for Windows player
version_info = client.clientversions.get(binary_type=BinaryType.WINDOWS_PLAYER, channel="LIVE")
print(version_info.version, version_info.client_version_upload, version_info.bootstrapper_version)
# Get application settings/feature flags for the PC desktop client
app_settings = client.applicationsettingses.get(application_name=ApplicationName.PC_DESKTOP_CLIENT)
print(len(app_settings.settings), list(app_settings.settings.items())[:3])
# Get the user's assigned deployment channel
channel = client.userchannels.get()
print(channel.channel_name)
Get the current client version, version upload hash, and bootstrapper version for a specific Roblox binary type and channel. Each binary type (WindowsPlayer, MacPlayer, WindowsStudio64, MacStudio) has its own independent version track. Non-LIVE channels may return different versions during staged rollouts.
| Param | Type | Description |
|---|---|---|
| channel | string | The deployment channel name. |
| binary_type | string | The Roblox binary type. |
{
"type": "object",
"fields": {
"version": "string - semantic version (e.g. 0.725.0.7251138)",
"bootstrapperVersion": "string - bootstrapper version string (e.g. 1, 6, 0, 7251138)",
"clientVersionUpload": "string - version upload identifier hash (e.g. version-76173e47a79145c7)"
},
"sample": {
"data": {
"version": "0.725.0.7251138",
"bootstrapperVersion": "1, 6, 0, 7251138",
"clientVersionUpload": "version-76173e47a79145c7"
},
"status": "success"
}
}About the Roblox API
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.
The Roblox API is a managed, monitored endpoint for clientsettings.roblox.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when clientsettings.roblox.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official clientsettings.roblox.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- 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 | 100 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.