Hello, we would like to provide an update on our previous post for announcing the deprecation of a few legacy endpoints.
We have decided to re-enable the GET https://www.roblox.com/places/api-get-details endpoint.; however, the response will be stripped of all fields except for AssetId and VisitedCount.
For the fields that are being removed from the places/api-get-details endpoint, here are alternate endpoints where you will be able to access those same fields.
For these fields:
Name, Description, Builder, BuilderId, Price
You can call the GET /v1/games/multiget-place-details endpoint on https://games.roblox.com. Here is a link to the documentation. An example request URL would look like this:
curl --location --request GET 'https://games.roblox.com/v1/games/multiget-place-details?placeIds=123&placeIds=456' \
--header 'Cookie: .ROBLOSECURITY=<your key>'
For the MaxPlayers field, you can call the GET /v2/places/{placeId} endpoint on https://develop.roblox.com. Here is a link to the public documentation. An example request URL would look like this:
curl --location --request GET 'https://develop.roblox.com/v2/places/{placeId} \
--header 'Cookie: .ROBLOSECURITY=<your key>'
And an example response would look like this:
{
“maxPlayerCount”: 6,
“socialSlotType”: “Automatic”,
“customSocialSlotsCount”: 2,
“allowCopying”: true,
“currentSavedVersion”: 1,
“isAllGenresAllowed”: true,
“maxPlayersAllowed”: 200,
“created”: “0001-01-01T00:00:00”,
“updated”: “0001-01-01T00:00:00”,
“id”: PlaceId,
“universeId”: UniverseId,
“name”: “Name”,
“description”: “Description”,
“isRootPlace”: true
}
Please let us know if you have any questions or concerns!