vrchatapi 1.22.2.dev4__py3-none-any.whl → 1.22.2.dev6__py3-none-any.whl

vrchatapi/__init__.py

@@ -7,7 +7,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -117,8 +117,10 @@ from vrchatapi.models.change_world_tags_request import ChangeWorldTagsRequest
 from vrchatapi.models.content_filter import ContentFilter
 from vrchatapi.models.create_avatar_moderation_request import CreateAvatarModerationRequest
 from vrchatapi.models.create_avatar_request import CreateAvatarRequest
+from vrchatapi.models.create_avatar_request_release_status import CreateAvatarRequestReleaseStatus
 from vrchatapi.models.create_calendar_event_request import CreateCalendarEventRequest
 from vrchatapi.models.create_file_request import CreateFileRequest
+from vrchatapi.models.create_file_request_mime_type import CreateFileRequestMIMEType
 from vrchatapi.models.create_file_version_request import CreateFileVersionRequest
 from vrchatapi.models.create_group_announcement_request import CreateGroupAnnouncementRequest
 from vrchatapi.models.create_group_gallery_request import CreateGroupGalleryRequest
@@ -127,11 +129,14 @@ from vrchatapi.models.create_group_post_request import CreateGroupPostRequest
 from vrchatapi.models.create_group_request import CreateGroupRequest
 from vrchatapi.models.create_group_role_request import CreateGroupRoleRequest
 from vrchatapi.models.create_instance_request import CreateInstanceRequest
+from vrchatapi.models.create_instance_request_region import CreateInstanceRequestRegion
 from vrchatapi.models.create_jam_submission_request import CreateJamSubmissionRequest
 from vrchatapi.models.create_listing_request import CreateListingRequest
 from vrchatapi.models.create_product_request import CreateProductRequest
+from vrchatapi.models.create_product_request_type import CreateProductRequestType
 from vrchatapi.models.create_prop_request import CreatePropRequest
 from vrchatapi.models.create_world_request import CreateWorldRequest
+from vrchatapi.models.create_world_request_release_status import CreateWorldRequestReleaseStatus
 from vrchatapi.models.current_user import CurrentUser
 from vrchatapi.models.current_user_login_response import CurrentUserLoginResponse
 from vrchatapi.models.current_user_presence import CurrentUserPresence
@@ -314,6 +319,7 @@ from vrchatapi.models.inventory_item import InventoryItem
 from vrchatapi.models.inventory_item_type import InventoryItemType
 from vrchatapi.models.inventory_metadata import InventoryMetadata
 from vrchatapi.models.inventory_notification_details import InventoryNotificationDetails
+from vrchatapi.models.inventory_sort_order import InventorySortOrder
 from vrchatapi.models.inventory_spawn import InventorySpawn
 from vrchatapi.models.inventory_template import InventoryTemplate
 from vrchatapi.models.inventory_user_attributes import InventoryUserAttributes
@@ -439,6 +445,7 @@ from vrchatapi.models.service_queue_stats import ServiceQueueStats
 from vrchatapi.models.service_status import ServiceStatus
 from vrchatapi.models.share_inventory_item_direct_request import ShareInventoryItemDirectRequest
 from vrchatapi.models.sort_option import SortOption
+from vrchatapi.models.sort_option_avatar import SortOptionAvatar
 from vrchatapi.models.sort_option_product_purchase import SortOptionProductPurchase
 from vrchatapi.models.sso_provider import SsoProvider
 from vrchatapi.models.sso_token import SsoToken
@@ -473,6 +480,7 @@ from vrchatapi.models.unavailable_world import UnavailableWorld
 from vrchatapi.models.unity_package import UnityPackage
 from vrchatapi.models.update_asset_review_notes_request import UpdateAssetReviewNotesRequest
 from vrchatapi.models.update_avatar_request import UpdateAvatarRequest
+from vrchatapi.models.update_avatar_request_release_status import UpdateAvatarRequestReleaseStatus
 from vrchatapi.models.update_calendar_event_request import UpdateCalendarEventRequest
 from vrchatapi.models.update_favorite_group_request import UpdateFavoriteGroupRequest
 from vrchatapi.models.update_group_gallery_request import UpdateGroupGalleryRequest
@@ -502,6 +510,7 @@ from vrchatapi.models.user_group_instance_list_response import UserGroupInstance
 from vrchatapi.models.user_note import UserNote
 from vrchatapi.models.user_note_target_user import UserNoteTargetUser
 from vrchatapi.models.user_response import UserResponse
+from vrchatapi.models.user_search_sort import UserSearchSort
 from vrchatapi.models.user_state import UserState
 from vrchatapi.models.user_status import UserStatus
 from vrchatapi.models.user_subscription import UserSubscription

vrchatapi/api/authentication_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 

vrchatapi/api/avatars_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -872,7 +872,7 @@ class AvatarsApi(object):
         :param featured: Filters on featured results.
         :type featured: bool
         :param sort: The sort order of the results.
-        :type sort: SortOption
+        :type sort: SortOptionAvatar
         :param n: The number of objects to return.
         :type n: int
         :param order: Result ordering
@@ -926,7 +926,7 @@ class AvatarsApi(object):
         :param featured: Filters on featured results.
         :type featured: bool
         :param sort: The sort order of the results.
-        :type sort: SortOption
+        :type sort: SortOptionAvatar
         :param n: The number of objects to return.
         :type n: int
         :param order: Result ordering
@@ -1519,7 +1519,7 @@ class AvatarsApi(object):
         :param featured: Filters on featured results.
         :type featured: bool
         :param sort: The sort order of the results.
-        :type sort: SortOption
+        :type sort: SortOptionAvatar
         :param user: Set to `me` for searching own avatars.
         :type user: str
         :param user_id: Filter by UserID.
@@ -1575,7 +1575,7 @@ class AvatarsApi(object):
         :param featured: Filters on featured results.
         :type featured: bool
         :param sort: The sort order of the results.
-        :type sort: SortOption
+        :type sort: SortOptionAvatar
         :param user: Set to `me` for searching own avatars.
         :type user: str
         :param user_id: Filter by UserID.

vrchatapi/api/calendar_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -532,6 +532,7 @@ class CalendarApi(object):
 
         response_types_map = {
             200: "CalendarEventDiscovery",
+            400: "Error",
             401: "Error",
         }
 

vrchatapi/api/economy_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -162,6 +162,7 @@ class EconomyApi(object):
 
         response_types_map = {
             200: "Product",
+            400: "Error",
             401: "Error",
         }
 
@@ -308,6 +309,7 @@ class EconomyApi(object):
 
         response_types_map = {
             200: "ProductListing",
+            400: "Error",
             401: "Error",
         }
 

vrchatapi/api/favorites_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -629,6 +629,7 @@ class FavoritesApi(object):
 
         response_types_map = {
             200: "FavoriteGroupContents",
+            400: "Error",
             401: "Error",
         }
 
@@ -798,6 +799,7 @@ class FavoritesApi(object):
 
         response_types_map = {
             200: "list[FavoriteGroup]",
+            400: "Error",
             401: "Error",
         }
 
@@ -943,6 +945,7 @@ class FavoritesApi(object):
 
         response_types_map = {
             200: "FavoriteGroupList",
+            400: "Error",
             401: "Error",
         }
 
@@ -1549,6 +1552,7 @@ class FavoritesApi(object):
 
         response_types_map = {
             200: "object",
+            400: "Error",
         }
 
         return self.api_client.call_api(

vrchatapi/api/files_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -159,6 +159,7 @@ class FilesApi(object):
 
         response_types_map = {
             200: "File",
+            400: "Error",
         }
 
         return self.api_client.call_api(

vrchatapi/api/friends_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 

vrchatapi/api/groups_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -500,6 +500,7 @@ class GroupsApi(object):
 
         response_types_map = {
             200: "GroupPost",
+            400: "Error",
             401: "Error",
         }
 
@@ -1222,6 +1223,7 @@ class GroupsApi(object):
 
         response_types_map = {
             200: "Group",
+            400: "Error",
             401: "Error",
         }
 
@@ -7424,6 +7426,7 @@ class GroupsApi(object):
 
         response_types_map = {
             200: "GroupMember",
+            400: "Error",
             401: "Error",
             403: "Error",
             404: "Error",
@@ -7592,6 +7595,7 @@ class GroupsApi(object):
 
         response_types_map = {
             200: "GroupPost",
+            400: "Error",
             401: "Error",
             403: "Error",
             404: "Success",

vrchatapi/api/instances_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -347,6 +347,155 @@ class InstancesApi(object):
             collection_formats=collection_formats,
             _request_auth=local_var_params.get('_request_auth'))
 
+    def get_active_instances(self, **kwargs):  # noqa: E501
+        """List Active Instances  # noqa: E501
+
+        Returns active instances, the most populated first.  # noqa: E501
+        This method makes a synchronous HTTP request by default. To make an
+        asynchronous HTTP request, please pass async_req=True
+
+        >>> thread = api.get_active_instances(async_req=True)
+        >>> result = thread.get()
+
+        :param n: The number of instances to return.
+        :type n: int
+        :param offset: A zero-based offset from the default object sorting from where search results start.
+        :type offset: int
+        :param async_req: Whether to execute the request asynchronously.
+        :type async_req: bool, optional
+        :param _preload_content: if False, the urllib3.HTTPResponse object will
+                                 be returned without reading/decoding response
+                                 data. Default is True.
+        :type _preload_content: bool, optional
+        :param _request_timeout: timeout setting for this request. If one
+                                 number provided, it will be total request
+                                 timeout. It can also be a pair (tuple) of
+                                 (connection, read) timeouts.
+        :return: Returns the result object.
+                 If the method is called asynchronously,
+                 returns the request thread.
+        :rtype: list[Instance]
+        """
+        kwargs['_return_http_data_only'] = True
+        return self.get_active_instances_with_http_info(**kwargs)  # noqa: E501
+
+    def get_active_instances_with_http_info(self, **kwargs):  # noqa: E501
+        """List Active Instances  # noqa: E501
+
+        Returns active instances, the most populated first.  # noqa: E501
+        This method makes a synchronous HTTP request by default. To make an
+        asynchronous HTTP request, please pass async_req=True
+
+        >>> thread = api.get_active_instances_with_http_info(async_req=True)
+        >>> result = thread.get()
+
+        :param n: The number of instances to return.
+        :type n: int
+        :param offset: A zero-based offset from the default object sorting from where search results start.
+        :type offset: int
+        :param async_req: Whether to execute the request asynchronously.
+        :type async_req: bool, optional
+        :param _return_http_data_only: response data without head status code
+                                       and headers
+        :type _return_http_data_only: bool, optional
+        :param _preload_content: if False, the urllib3.HTTPResponse object will
+                                 be returned without reading/decoding response
+                                 data. Default is True.
+        :type _preload_content: bool, optional
+        :param _request_timeout: timeout setting for this request. If one
+                                 number provided, it will be total request
+                                 timeout. It can also be a pair (tuple) of
+                                 (connection, read) timeouts.
+        :param _request_auth: set to override the auth_settings for an a single
+                              request; this effectively ignores the authentication
+                              in the spec for a single request.
+        :type _request_auth: dict, optional
+        :type _content_type: string, optional: force content-type for the request
+        :return: Returns the result object.
+                 If the method is called asynchronously,
+                 returns the request thread.
+        :rtype: tuple(list[Instance], status_code(int), headers(HTTPHeaderDict))
+        """
+
+        local_var_params = locals()
+
+        all_params = [
+            'n',
+            'offset'
+        ]
+        all_params.extend(
+            [
+                'async_req',
+                '_return_http_data_only',
+                '_preload_content',
+                '_request_timeout',
+                '_request_auth',
+                '_content_type',
+                '_headers'
+            ]
+        )
+
+        for key, val in six.iteritems(local_var_params['kwargs']):
+            if key not in all_params:
+                raise ApiTypeError(
+                    "Got an unexpected keyword argument '%s'"
+                    " to method get_active_instances" % key
+                )
+            local_var_params[key] = val
+        del local_var_params['kwargs']
+
+        if self.api_client.client_side_validation and 'n' in local_var_params and local_var_params['n'] > 50:  # noqa: E501
+            raise ApiValueError("Invalid value for parameter `n` when calling `get_active_instances`, must be a value less than or equal to `50`")  # noqa: E501
+        if self.api_client.client_side_validation and 'n' in local_var_params and local_var_params['n'] < 1:  # noqa: E501
+            raise ApiValueError("Invalid value for parameter `n` when calling `get_active_instances`, must be a value greater than or equal to `1`")  # noqa: E501
+        if self.api_client.client_side_validation and 'offset' in local_var_params and local_var_params['offset'] < 0:  # noqa: E501
+            raise ApiValueError("Invalid value for parameter `offset` when calling `get_active_instances`, must be a value greater than or equal to `0`")  # noqa: E501
+        collection_formats = {}
+
+        path_params = {}
+
+        query_params = []
+        if local_var_params.get('n') is not None:  # noqa: E501
+            query_params.append(('n', local_var_params['n']))  # noqa: E501
+        if local_var_params.get('offset') is not None:  # noqa: E501
+            query_params.append(('offset', local_var_params['offset']))  # noqa: E501
+
+        header_params = dict(local_var_params.get('_headers', {}))
+
+        form_params = []
+        local_var_files = {}
+
+        body_params = None
+        # HTTP header `Accept`
+        header_params['Accept'] = self.api_client.select_header_accept(
+            ['application/json'])  # noqa: E501
+
+        # Authentication setting
+        auth_settings = ['authCookie']  # noqa: E501
+
+        response_types_map = {
+            200: "list[Instance]",
+            400: "Error",
+            401: "Error",
+        }
+
+        return self.api_client.call_api(
+            '/instances/active', 'GET',
+            path_params,
+            query_params,
+            header_params,
+            body=body_params,
+            post_params=form_params,
+            files=local_var_files,
+            response_types_map=response_types_map,
+            auth_settings=auth_settings,
+            async_req=local_var_params.get('async_req'),
+            _return_http_data_only=local_var_params.get('_return_http_data_only'),  # noqa: E501
+            _preload_content=local_var_params.get('_preload_content', True),
+            _request_timeout=local_var_params.get('_request_timeout'),
+            collection_formats=collection_formats,
+            _request_auth=local_var_params.get('_request_auth'))
+
     def get_instance(self, world_id, instance_id, **kwargs):  # noqa: E501
         """Get Instance  # noqa: E501
 

vrchatapi/api/inventory_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -625,7 +625,7 @@ class InventoryApi(object):
         :param equip_slot: Filter for inventory retrieval.
         :type equip_slot: InventoryEquipSlot
         :param order: Sort order for inventory retrieval.
-        :type order: str
+        :type order: InventorySortOrder
         :param tags: Filter tags for inventory retrieval (comma-separated).
         :type tags: str
         :param types: Filter for inventory retrieval.
@@ -679,7 +679,7 @@ class InventoryApi(object):
         :param equip_slot: Filter for inventory retrieval.
         :type equip_slot: InventoryEquipSlot
         :param order: Sort order for inventory retrieval.
-        :type order: str
+        :type order: InventorySortOrder
         :param tags: Filter tags for inventory retrieval (comma-separated).
         :type tags: str
         :param types: Filter for inventory retrieval.
@@ -814,6 +814,7 @@ class InventoryApi(object):
 
         response_types_map = {
             200: "Inventory",
+            400: "Error",
             401: "Error",
             403: "Error",
         }

vrchatapi/api/invite_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 

vrchatapi/api/jams_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 

vrchatapi/api/miscellaneous_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 

vrchatapi/api/notifications_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 

vrchatapi/api/playermoderation_api.py

@@ -5,7 +5,7 @@
 
     This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501
 
-    The version of the OpenAPI document: 1.22.2-nightly.4
+    The version of the OpenAPI document: 1.22.2-nightly.6
     Generated by: https://openapi-generator.tech
 """
 
@@ -286,6 +286,7 @@ class PlayermoderationApi(object):
 
         response_types_map = {
             200: "list[PlayerModeration]",
+            400: "Error",
             401: "Error",
         }
 
@@ -432,6 +433,7 @@ class PlayermoderationApi(object):
 
         response_types_map = {
             200: "PlayerModeration",
+            400: "Error",
             401: "Error",
         }
 
@@ -578,6 +580,7 @@ class PlayermoderationApi(object):
 
         response_types_map = {
             200: "Success",
+            400: "Error",
             401: "Error",
         }