A bug seems to happen on my side with a mysterious ‘universe.place:read’ scope missing in ‘universe’ scopes. When I looked into all ‘universe’ related scopes, I didnt find a single trace of this mysterious ‘read’ scope, only ‘write’ one.
How did I run into this is simple:
I found out about /cloud/v2/universes/{universe}/places to get information about universe places
Configured my script to make requests to this endpoint.
The route you’ve referenced isn’t part of our public API surface, so the non-200 error you’re seeing is expected. Re our documentation, we only support Get and Update Place on Open Cloud at the moment. This list places endpoint on open cloud is currently in development and set to release soon though!
While not recommended due to the usage of cookie authentication, an alternative is the Develop API’s List Places endpoint, which fetches a list of places for a particular universe id.