[Action Needed] Sunsetting api.roblox.com

If you want to take a risk, use apis.roblox.com/universes/v1/places/1818/universe. Not publicly documented as of right now, and doesn’t require authentication.

2 Likes

Thanks for the feedback on the deprecation of GET /universes/get-universe-containing-place.

We have created a new endpoint that does not require authentication. It allows you to fetch the universe id, given a place id.

https://apis.roblox.com/universes/v1/places/{placeId}/universe

8 Likes

A replacement endpoint for POST /universes/create is now available. Check out the original post for details.

The new endpoint uses templatePlaceId, not templatePlaceIdToUse.

Can you make an similar endpoint for GET /users/get-by-username?

It would be much easier to use an endpoint as simple as the one on api.roblox.com instead of the current replacement on the Users API.

Hello, would it be possible to @mention the web developers group the next time there is a change? When I first checked this post the endpoint i was using was still operational but there wasn’t a replacement yet. In November that endpoint got removed and my application stopped working because I was not aware of the removal. This would help our applications not to break as we can’t look at this topic every day.

Not documented, but you could try this one (it’s what MarketplaceService uses):

https://economy.roblox.com/v1/game-pass/{gamepassId}/game-pass-product-info

Use this instead

1 Like

No. The endpoint is self-explanatory. It’s for gamepasses only.

This endpoint doesn’t returns prices for limiteds?
https://economy.roblox.com/v2/assets/124730194/details

1 Like

There is now a new presence endpoint that returns the accurate lastOnline

https://presence.roblox.com/v1/presence/last-online

The docs:

https://presence.roblox.com/docs/index.html

Credit to @juliaoverflow for finding it out

3 Likes

@ValiantWind is correct. The api-proxy online-status endpoint will be deprecated on January 31st. A supplementary presence api endpoint (v1/presence/last-online) which provides accurate last online information has been released as a partial replacement for api-proxy online-status. Using this endpoint and the existing /v1/presence/users endpoint, it is possible to retrieve all information currently available from api-proxy online-status. Official deprecation announcement: Official List of Deprecated Web Endpoints - #46 by Radicalius.

4 Likes

I’m getting this error
The custom error module does not recognize this error.
on the old API after a few requests

1 Like

Any update on these two? They’re decommissioned so an alternative would be very helpful. Especially the productdetails endpoint since I haven’t found any alternative yet.

Until alternatives are provided, https://economy.roblox.com/v1/game-pass/GAME_PASS_ID/game-pass-product-info for passes and https://economy.roblox.com/v2/developer-products/PRODUCT_ID/details for products.

Roblox will probably also deprecate the pass details endpoint in the future, so it’s best to use https://apis.roblox.com/game-passes/v1/game-passes/GAME_PASS_ID/product-info for passes long-term.

It’s saying that HttpService is not allowed to access ROBLOX resources, me idk what to do

Why are there no docs for https://apis.roblox.com/

HTTP ERROR 404

You need to use a proxy in order to use the Roblox Web API with HttpService

Because there aren’t any official docs for apis.roblox.com.

1 Like

Hi, I’m using one of the avatar.roblox.com endpoints (currently-wearing) and I’m being HEAVILY rate-limited.

I’m trying to send about 1 request per minute and it isn’t working, with 429 errors (TOO MANY REQUESTS).

I’m using this to check if a user is on-duty (i.e. wearing certain avatar items) every minute, and it was working fine until recently.

The initial post says to leave a reply if experiencing rate-limits, so here it is…

Isn’t doing it per minute a bit much? I mean it wouldn’t make that much of a difference to do a check every 5 minutes or so. It would be very inconvenient for the user to switch outfits back and worth every 5 minutes just to pass the check, so it should be sufficient enough.

Once a minute isn’t really excessive imo considering some APIs allow requests every second (not necessarily Roblox).

And yes, it actually would make a decent difference checking every 5 mins as let’s say someone went off duty at 34 minutes - they’d lose 4 minutes as the precious check would have been at 30 mins and the next one would only be at 35. But, on the other hand, I do suppose losing a max of 4 minutes isn’t a huge deal so this is definitely something I can consider if Roblox doesn’t manage to help regarding this situation

1 Like