vrchatapi 1.23.1.dev4__py3-none-any.whl → 1.23.1.dev5__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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 
@@ -105,6 +105,7 @@ from vrchatapi.models.calendar_event_category import CalendarEventCategory
 from vrchatapi.models.calendar_event_discovery import CalendarEventDiscovery
 from vrchatapi.models.calendar_event_discovery_inclusion import CalendarEventDiscoveryInclusion
 from vrchatapi.models.calendar_event_discovery_scope import CalendarEventDiscoveryScope
+from vrchatapi.models.calendar_event_discovery_sort import CalendarEventDiscoverySort
 from vrchatapi.models.calendar_event_frequency import CalendarEventFrequency
 from vrchatapi.models.calendar_event_occurrence_kind import CalendarEventOccurrenceKind
 from vrchatapi.models.calendar_event_platform import CalendarEventPlatform
@@ -115,6 +116,7 @@ from vrchatapi.models.calendar_event_user_interest import CalendarEventUserInter
 from vrchatapi.models.change_user_tags_request import ChangeUserTagsRequest
 from vrchatapi.models.change_world_tags_request import ChangeWorldTagsRequest
 from vrchatapi.models.content_filter import ContentFilter
+from vrchatapi.models.cosmetic_item_type import CosmeticItemType
 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
@@ -145,6 +147,11 @@ from vrchatapi.models.developer_type import DeveloperType
 from vrchatapi.models.disable2_fa_result import Disable2FAResult
 from vrchatapi.models.discord_details import DiscordDetails
 from vrchatapi.models.dynamic_content_row import DynamicContentRow
+from vrchatapi.models.dynamic_content_row_avatars import DynamicContentRowAvatars
+from vrchatapi.models.dynamic_content_row_base import DynamicContentRowBase
+from vrchatapi.models.dynamic_content_row_events import DynamicContentRowEvents
+from vrchatapi.models.dynamic_content_row_instances import DynamicContentRowInstances
+from vrchatapi.models.dynamic_content_row_worlds import DynamicContentRowWorlds
 from vrchatapi.models.earnings_metrics import EarningsMetrics
 from vrchatapi.models.earnings_metrics_totals import EarningsMetricsTotals
 from vrchatapi.models.economy_account import EconomyAccount
@@ -180,6 +187,8 @@ from vrchatapi.models.file import File
 from vrchatapi.models.file_analysis import FileAnalysis
 from vrchatapi.models.file_analysis_avatar_stats import FileAnalysisAvatarStats
 from vrchatapi.models.file_data import FileData
+from vrchatapi.models.file_data_category import FileDataCategory
+from vrchatapi.models.file_data_type import FileDataType
 from vrchatapi.models.file_status import FileStatus
 from vrchatapi.models.file_upload_url import FileUploadURL
 from vrchatapi.models.file_version import FileVersion
@@ -187,6 +196,7 @@ from vrchatapi.models.file_version_upload_status import FileVersionUploadStatus
 from vrchatapi.models.finish_file_data_upload_request import FinishFileDataUploadRequest
 from vrchatapi.models.follow_calendar_event_request import FollowCalendarEventRequest
 from vrchatapi.models.friend_status import FriendStatus
+from vrchatapi.models.frontend_variant import FrontendVariant
 from vrchatapi.models.group import Group
 from vrchatapi.models.group_access_type import GroupAccessType
 from vrchatapi.models.group_announcement import GroupAnnouncement
@@ -289,14 +299,37 @@ from vrchatapi.models.image_animation_style import ImageAnimationStyle
 from vrchatapi.models.image_loop_style import ImageLoopStyle
 from vrchatapi.models.image_mask import ImageMask
 from vrchatapi.models.info_push import InfoPush
+from vrchatapi.models.info_push_accessories_category_data import InfoPushAccessoriesCategoryData
+from vrchatapi.models.info_push_avatar_category_data import InfoPushAvatarCategoryData
+from vrchatapi.models.info_push_banner_data import InfoPushBannerData
+from vrchatapi.models.info_push_base import InfoPushBase
+from vrchatapi.models.info_push_command import InfoPushCommand
+from vrchatapi.models.info_push_content import InfoPushContent
+from vrchatapi.models.info_push_content_calendar_entries import InfoPushContentCalendarEntries
+from vrchatapi.models.info_push_content_instances import InfoPushContentInstances
+from vrchatapi.models.info_push_content_shelf import InfoPushContentShelf
+from vrchatapi.models.info_push_content_shelf_data import InfoPushContentShelfData
+from vrchatapi.models.info_push_content_unknown import InfoPushContentUnknown
 from vrchatapi.models.info_push_data import InfoPushData
 from vrchatapi.models.info_push_data_article import InfoPushDataArticle
 from vrchatapi.models.info_push_data_article_content import InfoPushDataArticleContent
 from vrchatapi.models.info_push_data_call_to_action import InfoPushDataCallToAction
 from vrchatapi.models.info_push_data_category import InfoPushDataCategory
+from vrchatapi.models.info_push_data_category_articles import InfoPushDataCategoryArticles
+from vrchatapi.models.info_push_data_category_base import InfoPushDataCategoryBase
+from vrchatapi.models.info_push_data_category_groups import InfoPushDataCategoryGroups
+from vrchatapi.models.info_push_data_category_unknown import InfoPushDataCategoryUnknown
+from vrchatapi.models.info_push_data_category_worlds import InfoPushDataCategoryWorlds
 from vrchatapi.models.info_push_data_clickable import InfoPushDataClickable
 from vrchatapi.models.info_push_data_content_source import InfoPushDataContentSource
+from vrchatapi.models.info_push_data_content_source_base import InfoPushDataContentSourceBase
+from vrchatapi.models.info_push_data_content_source_calendar_discover import InfoPushDataContentSourceCalendarDiscover
+from vrchatapi.models.info_push_data_content_source_calendar_discover_params import InfoPushDataContentSourceCalendarDiscoverParams
+from vrchatapi.models.info_push_data_content_source_instance_discover import InfoPushDataContentSourceInstanceDiscover
+from vrchatapi.models.info_push_data_content_source_instance_discover_params import InfoPushDataContentSourceInstanceDiscoverParams
 from vrchatapi.models.info_push_data_content_source_pagination import InfoPushDataContentSourcePagination
+from vrchatapi.models.info_push_data_content_source_params import InfoPushDataContentSourceParams
+from vrchatapi.models.info_push_data_content_source_unknown import InfoPushDataContentSourceUnknown
 from vrchatapi.models.info_push_data_control import InfoPushDataControl
 from vrchatapi.models.info_push_data_control_option import InfoPushDataControlOption
 from vrchatapi.models.info_push_data_delivery_behavior import InfoPushDataDeliveryBehavior
@@ -305,14 +338,30 @@ from vrchatapi.models.info_push_data_presentation import InfoPushDataPresentatio
 from vrchatapi.models.info_push_data_promotion import InfoPushDataPromotion
 from vrchatapi.models.info_push_data_promotion_notification import InfoPushDataPromotionNotification
 from vrchatapi.models.info_push_data_search import InfoPushDataSearch
+from vrchatapi.models.info_push_discovery_category_data import InfoPushDiscoveryCategoryData
 from vrchatapi.models.info_push_embedded_link import InfoPushEmbeddedLink
 from vrchatapi.models.info_push_experiment import InfoPushExperiment
+from vrchatapi.models.info_push_help_article_data import InfoPushHelpArticleData
+from vrchatapi.models.info_push_help_topic_data import InfoPushHelpTopicData
 from vrchatapi.models.info_push_ips_query import InfoPushIpsQuery
+from vrchatapi.models.info_push_loading_screen_banner_data import InfoPushLoadingScreenBannerData
+from vrchatapi.models.info_push_marketplace_page_data import InfoPushMarketplacePageData
+from vrchatapi.models.info_push_onboarding_avatar_data import InfoPushOnboardingAvatarData
+from vrchatapi.models.info_push_other_data import InfoPushOtherData
+from vrchatapi.models.info_push_search_data import InfoPushSearchData
+from vrchatapi.models.info_push_tile_data import InfoPushTileData
+from vrchatapi.models.info_push_untyped import InfoPushUntyped
+from vrchatapi.models.info_push_url_consent_screen_data import InfoPushUrlConsentScreenData
+from vrchatapi.models.info_push_version_data import InfoPushVersionData
+from vrchatapi.models.info_push_world_category_data import InfoPushWorldCategoryData
 from vrchatapi.models.instance import Instance
 from vrchatapi.models.instance_category import InstanceCategory
 from vrchatapi.models.instance_content_settings import InstanceContentSettings
 from vrchatapi.models.instance_discovery import InstanceDiscovery
+from vrchatapi.models.instance_discovery_boost import InstanceDiscoveryBoost
+from vrchatapi.models.instance_discovery_mode import InstanceDiscoveryMode
 from vrchatapi.models.instance_discovery_platform import InstanceDiscoveryPlatform
+from vrchatapi.models.instance_discovery_world_pool import InstanceDiscoveryWorldPool
 from vrchatapi.models.instance_platforms import InstancePlatforms
 from vrchatapi.models.instance_region import InstanceRegion
 from vrchatapi.models.instance_short_name_response import InstanceShortNameResponse
@@ -429,6 +478,7 @@ from vrchatapi.models.product_purchase_location_type import ProductPurchaseLocat
 from vrchatapi.models.product_purchase_product import ProductPurchaseProduct
 from vrchatapi.models.product_purchase_record import ProductPurchaseRecord
 from vrchatapi.models.product_type import ProductType
+from vrchatapi.models.profile_background_type import ProfileBackgroundType
 from vrchatapi.models.profile_group import ProfileGroup
 from vrchatapi.models.profile_groups import ProfileGroups
 from vrchatapi.models.profile_represented_group import ProfileRepresentedGroup
@@ -456,6 +506,7 @@ from vrchatapi.models.reward_redemption_data import RewardRedemptionData
 from vrchatapi.models.reward_redemption_request import RewardRedemptionRequest
 from vrchatapi.models.reward_redemption_result import RewardRedemptionResult
 from vrchatapi.models.route_not_implemented import RouteNotImplemented
+from vrchatapi.models.search_worlds_user import SearchWorldsUser
 from vrchatapi.models.seller_eligibility import SellerEligibility
 from vrchatapi.models.sent_notification import SentNotification
 from vrchatapi.models.sent_notification_base import SentNotificationBase

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 
@@ -375,6 +375,10 @@ class CalendarApi(object):
         :type n: int
         :param next_cursor: Cursor returned from previous calendar discovery queries (see nextCursor property of the schema CalendarEventDiscovery).
         :type next_cursor: str
+        :param require_linked_instance:
+        :type require_linked_instance: bool
+        :param upcoming_sort:
+        :type upcoming_sort: CalendarEventDiscoverySort
         :param async_req: Whether to execute the request asynchronously.
         :type async_req: bool, optional
         :param _preload_content: if False, the urllib3.HTTPResponse object will
@@ -425,6 +429,10 @@ class CalendarApi(object):
         :type n: int
         :param next_cursor: Cursor returned from previous calendar discovery queries (see nextCursor property of the schema CalendarEventDiscovery).
         :type next_cursor: str
+        :param require_linked_instance:
+        :type require_linked_instance: bool
+        :param upcoming_sort:
+        :type upcoming_sort: CalendarEventDiscoverySort
         :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
@@ -462,7 +470,9 @@ class CalendarApi(object):
             'minimum_remaining_minutes',
             'upcoming_offset_minutes',
             'n',
-            'next_cursor'
+            'next_cursor',
+            'require_linked_instance',
+            'upcoming_sort'
         ]
         all_params.extend(
             [
@@ -516,6 +526,10 @@ class CalendarApi(object):
             query_params.append(('n', local_var_params['n']))  # noqa: E501
         if local_var_params.get('next_cursor') is not None:  # noqa: E501
             query_params.append(('nextCursor', local_var_params['next_cursor']))  # noqa: E501
+        if local_var_params.get('require_linked_instance') is not None:  # noqa: E501
+            query_params.append(('requireLinkedInstance', local_var_params['require_linked_instance']))  # noqa: E501
+        if local_var_params.get('upcoming_sort') is not None:  # noqa: E501
+            query_params.append(('upcomingSort', local_var_params['upcoming_sort']))  # noqa: E501
 
         header_params = dict(local_var_params.get('_headers', {}))
 

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 
@@ -786,7 +786,7 @@ class FilesApi(object):
         :param version_id: Version ID of the asset. (required)
         :type version_id: int
         :param file_type: Type of file. (required)
-        :type file_type: str
+        :type file_type: FileDataType
         :param finish_file_data_upload_request: Please see documentation on ETag's: [https://teppen.io/2018/06/23/aws_s3_etags/](https://teppen.io/2018/06/23/aws_s3_etags/)  ETag's should NOT be present when uploading a `signature`.
         :type finish_file_data_upload_request: FinishFileDataUploadRequest
         :param async_req: Whether to execute the request asynchronously.
@@ -822,7 +822,7 @@ class FilesApi(object):
         :param version_id: Version ID of the asset. (required)
         :type version_id: int
         :param file_type: Type of file. (required)
-        :type file_type: str
+        :type file_type: FileDataType
         :param finish_file_data_upload_request: Please see documentation on ETag's: [https://teppen.io/2018/06/23/aws_s3_etags/](https://teppen.io/2018/06/23/aws_s3_etags/)  ETag's should NOT be present when uploading a `signature`.
         :type finish_file_data_upload_request: FinishFileDataUploadRequest
         :param async_req: Whether to execute the request asynchronously.
@@ -1848,7 +1848,7 @@ class FilesApi(object):
         :param version_id: Version ID of the asset. (required)
         :type version_id: int
         :param file_type: Type of file. (required)
-        :type file_type: str
+        :type file_type: FileDataType
         :param async_req: Whether to execute the request asynchronously.
         :type async_req: bool, optional
         :param _preload_content: if False, the urllib3.HTTPResponse object will
@@ -1882,7 +1882,7 @@ class FilesApi(object):
         :param version_id: Version ID of the asset. (required)
         :type version_id: int
         :param file_type: Type of file. (required)
-        :type file_type: str
+        :type file_type: FileDataType
         :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
@@ -2317,7 +2317,7 @@ class FilesApi(object):
         :param version_id: Version ID of the asset. (required)
         :type version_id: int
         :param file_type: Type of file. (required)
-        :type file_type: str
+        :type file_type: FileDataType
         :param part_number: The part number to start uploading. If not provided, the first part will be started.
         :type part_number: int
         :param async_req: Whether to execute the request asynchronously.
@@ -2353,7 +2353,7 @@ class FilesApi(object):
         :param version_id: Version ID of the asset. (required)
         :type version_id: int
         :param file_type: Type of file. (required)
-        :type file_type: str
+        :type file_type: FileDataType
         :param part_number: The part number to start uploading. If not provided, the first part will be started.
         :type part_number: int
         :param async_req: Whether to execute the request asynchronously.

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 
@@ -371,6 +371,24 @@ class InstancesApi(object):
         :type vibe: list[str]
         :param category:
         :type category: str
+        :param any_world_tag: Not every account may use it; the others are answered 403.
+        :type any_world_tag: list[str]
+        :param boost: Only `GET /infoPush/{entryId}/content` accepts it; this route answers 400 to any value.
+        :type boost: list[InstanceDiscoveryBoost]
+        :param group_hosted:
+        :type group_hosted: bool
+        :param max_occupants:
+        :type max_occupants: int
+        :param min_occupants:
+        :type min_occupants: int
+        :param min_spots_left: Not every account may use it; the others are answered 403.
+        :type min_spots_left: int
+        :param mode:
+        :type mode: InstanceDiscoveryMode
+        :param not_world_tag: Not every account may use it; the others are answered 403.
+        :type not_world_tag: list[str]
+        :param world_pool:
+        :type world_pool: InstanceDiscoveryWorldPool
         :param async_req: Whether to execute the request asynchronously.
         :type async_req: bool, optional
         :param _preload_content: if False, the urllib3.HTTPResponse object will
@@ -413,6 +431,24 @@ class InstancesApi(object):
         :type vibe: list[str]
         :param category:
         :type category: str
+        :param any_world_tag: Not every account may use it; the others are answered 403.
+        :type any_world_tag: list[str]
+        :param boost: Only `GET /infoPush/{entryId}/content` accepts it; this route answers 400 to any value.
+        :type boost: list[InstanceDiscoveryBoost]
+        :param group_hosted:
+        :type group_hosted: bool
+        :param max_occupants:
+        :type max_occupants: int
+        :param min_occupants:
+        :type min_occupants: int
+        :param min_spots_left: Not every account may use it; the others are answered 403.
+        :type min_spots_left: int
+        :param mode:
+        :type mode: InstanceDiscoveryMode
+        :param not_world_tag: Not every account may use it; the others are answered 403.
+        :type not_world_tag: list[str]
+        :param world_pool:
+        :type world_pool: InstanceDiscoveryWorldPool
         :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
@@ -446,7 +482,16 @@ class InstancesApi(object):
             'world_id',
             'group_id',
             'vibe',
-            'category'
+            'category',
+            'any_world_tag',
+            'boost',
+            'group_hosted',
+            'max_occupants',
+            'min_occupants',
+            'min_spots_left',
+            'mode',
+            'not_world_tag',
+            'world_pool'
         ]
         all_params.extend(
             [
@@ -495,6 +540,27 @@ class InstancesApi(object):
             collection_formats['vibe'] = 'multi'  # noqa: E501
         if local_var_params.get('category') is not None:  # noqa: E501
             query_params.append(('category', local_var_params['category']))  # noqa: E501
+        if local_var_params.get('any_world_tag') is not None:  # noqa: E501
+            query_params.append(('anyWorldTag', local_var_params['any_world_tag']))  # noqa: E501
+            collection_formats['anyWorldTag'] = 'multi'  # noqa: E501
+        if local_var_params.get('boost') is not None:  # noqa: E501
+            query_params.append(('boost', local_var_params['boost']))  # noqa: E501
+            collection_formats['boost'] = 'multi'  # noqa: E501
+        if local_var_params.get('group_hosted') is not None:  # noqa: E501
+            query_params.append(('groupHosted', local_var_params['group_hosted']))  # noqa: E501
+        if local_var_params.get('max_occupants') is not None:  # noqa: E501
+            query_params.append(('maxOccupants', local_var_params['max_occupants']))  # noqa: E501
+        if local_var_params.get('min_occupants') is not None:  # noqa: E501
+            query_params.append(('minOccupants', local_var_params['min_occupants']))  # noqa: E501
+        if local_var_params.get('min_spots_left') is not None:  # noqa: E501
+            query_params.append(('minSpotsLeft', local_var_params['min_spots_left']))  # noqa: E501
+        if local_var_params.get('mode') is not None:  # noqa: E501
+            query_params.append(('mode', local_var_params['mode']))  # noqa: E501
+        if local_var_params.get('not_world_tag') is not None:  # noqa: E501
+            query_params.append(('notWorldTag', local_var_params['not_world_tag']))  # noqa: E501
+            collection_formats['notWorldTag'] = 'multi'  # noqa: E501
+        if local_var_params.get('world_pool') is not None:  # noqa: E501
+            query_params.append(('worldPool', local_var_params['world_pool']))  # noqa: E501
 
         header_params = dict(local_var_params.get('_headers', {}))
 
@@ -513,6 +579,7 @@ class InstancesApi(object):
             200: "InstanceDiscovery",
             400: "Error",
             401: "Error",
+            403: "Error",
         }
 
         return self.api_client.call_api(

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """
 
@@ -478,7 +478,7 @@ class InventoryApi(object):
         >>> result = thread.get()
 
         :param item_type: The kind of cosmetic to list. (required)
-        :type item_type: str
+        :type item_type: CosmeticItemType
         :param async_req: Whether to execute the request asynchronously.
         :type async_req: bool, optional
         :param _preload_content: if False, the urllib3.HTTPResponse object will
@@ -508,7 +508,7 @@ class InventoryApi(object):
         >>> result = thread.get()
 
         :param item_type: The kind of cosmetic to list. (required)
-        :type item_type: str
+        :type item_type: CosmeticItemType
         :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

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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     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.23.1-nightly.4
+    The version of the OpenAPI document: 1.23.1-nightly.5
     Generated by: https://openapi-generator.tech
 """