Get User Worlds
Changed onLists the worlds owned by a user. Public callers see the user's Public worlds only; the user themselves (or an admin) also see their non-Public worlds -- the same semantics as GET /v2/worlds?users_id=N.
Request
- Base URLhttps://api.sidequestvr.com
- URLhttps://api.sidequestvr.com/v2/users/{route_users_id}/worlds
- Authnone declared
Path parameters
The unique users id, or 'me' for the calling user
Query parameters
Skips a number of objects from the start of the list. Used for paging.
Limits the number of objects returned.
Filters the returned rows by the ID of the user that owns the world
- 100 - Only the world owner can join
- 200 - The owner and the owner's accepted friends can join
- 250 - Friends+: the owner, the owner's accepted friends, and their accepted friends can join
- 300 - The owner plus owners/moderators of communities the world is attached to (Approved attachments only)
- 400 - The owner plus any non-blocked member of communities the world is attached to (Approved attachments only)
- 1000 - Anyone can join, including anonymous users
Filters the returned rows by the world's access level
Filters the returned rows by the name of the world. The % (url encoded as %25) can be included in the string as a wildcard.
Filters the returned rows by true when the world is hosted on a third-party URL (verified via the sidequest-space-verification meta tag) instead of SideQuest hosting
Filters the returned rows by whether this is a staff pick
Filters the returned rows by whether this is a community pick
Sorts the returned object by one or more parameters. Multiple values can be separated by a comma for sorting on multiple fields.
- name - The name of the world
- created_at - When the world was created
- status - The world's access level
- top - The world's upvote count
- hot - The world's hot score
- attendance - How many space sessions the world has hosted
- time_spent - The total time users have spent in the world
Orders the results in descending order based on the sortOn specified. If there are multiple sortOns specified, multiple values can be separated by a comma for each corresponding sortOn.
Response
Success
Example response
[
{
"created_at": "1970-04-20 07:10:00+00",
"last_modified": "1970-04-20 07:10:00+00"
}
]Changes
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info
- info
endpoint added
- info