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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (564) hide show
  1. vrchatapi/__init__.py +1 -1
  2. vrchatapi/api/authentication_api.py +1 -1
  3. vrchatapi/api/avatars_api.py +1 -1
  4. vrchatapi/api/calendar_api.py +1 -1
  5. vrchatapi/api/economy_api.py +1 -1
  6. vrchatapi/api/favorites_api.py +1 -1
  7. vrchatapi/api/files_api.py +1 -1
  8. vrchatapi/api/friends_api.py +1 -1
  9. vrchatapi/api/groups_api.py +1 -1
  10. vrchatapi/api/instances_api.py +1 -1
  11. vrchatapi/api/inventory_api.py +1 -1
  12. vrchatapi/api/invite_api.py +1 -1
  13. vrchatapi/api/jams_api.py +1 -1
  14. vrchatapi/api/miscellaneous_api.py +1 -1
  15. vrchatapi/api/notifications_api.py +1 -1
  16. vrchatapi/api/playermoderation_api.py +1 -1
  17. vrchatapi/api/prints_api.py +1 -1
  18. vrchatapi/api/props_api.py +1 -1
  19. vrchatapi/api/users_api.py +3 -3
  20. vrchatapi/api/worlds_api.py +1 -1
  21. vrchatapi/api_client.py +1 -1
  22. vrchatapi/configuration.py +2 -2
  23. vrchatapi/exceptions.py +1 -1
  24. vrchatapi/models/__init__.py +1 -1
  25. vrchatapi/models/account_deletion_log.py +1 -1
  26. vrchatapi/models/add_favorite_request.py +1 -1
  27. vrchatapi/models/add_group_gallery_image_request.py +1 -1
  28. vrchatapi/models/admin_asset_bundle.py +1 -1
  29. vrchatapi/models/admin_unity_package.py +1 -1
  30. vrchatapi/models/age_verification_status.py +1 -1
  31. vrchatapi/models/age_verification_status_result.py +1 -1
  32. vrchatapi/models/agreement.py +1 -1
  33. vrchatapi/models/agreement_code.py +1 -1
  34. vrchatapi/models/agreement_request.py +1 -1
  35. vrchatapi/models/agreement_status.py +1 -1
  36. vrchatapi/models/api_config.py +1 -1
  37. vrchatapi/models/api_config_access_logs_urls.py +1 -1
  38. vrchatapi/models/api_config_announcement.py +1 -1
  39. vrchatapi/models/api_config_audio_config.py +1 -1
  40. vrchatapi/models/api_config_avatar_perf_limiter.py +1 -1
  41. vrchatapi/models/api_config_constants.py +1 -1
  42. vrchatapi/models/api_config_constants_groups.py +1 -1
  43. vrchatapi/models/api_config_constants_instance.py +1 -1
  44. vrchatapi/models/api_config_constants_instancepopulationbrackets.py +1 -1
  45. vrchatapi/models/api_config_constants_instancepopulationbracketscrowded.py +1 -1
  46. vrchatapi/models/api_config_constants_instancepopulationbracketsfew.py +1 -1
  47. vrchatapi/models/api_config_constants_instancepopulationbracketsmany.py +1 -1
  48. vrchatapi/models/api_config_constants_language.py +1 -1
  49. vrchatapi/models/api_config_download_url_list.py +1 -1
  50. vrchatapi/models/api_config_event_shelf_campaign.py +1 -1
  51. vrchatapi/models/api_config_events.py +1 -1
  52. vrchatapi/models/api_config_ios_version.py +1 -1
  53. vrchatapi/models/api_config_loading_screen_weights.py +1 -1
  54. vrchatapi/models/api_config_low_memory_go_home_timeout_value.py +1 -1
  55. vrchatapi/models/api_config_min_supported_client_build_number.py +1 -1
  56. vrchatapi/models/api_config_offline_analysis.py +1 -1
  57. vrchatapi/models/api_config_profile_defaults.py +1 -1
  58. vrchatapi/models/api_health.py +1 -1
  59. vrchatapi/models/avatar.py +1 -1
  60. vrchatapi/models/avatar_moderation.py +1 -1
  61. vrchatapi/models/avatar_moderation_created.py +1 -1
  62. vrchatapi/models/avatar_moderation_type.py +1 -1
  63. vrchatapi/models/avatar_performance.py +1 -1
  64. vrchatapi/models/avatar_published_listings_inner.py +1 -1
  65. vrchatapi/models/avatar_style.py +1 -1
  66. vrchatapi/models/avatar_styles.py +1 -1
  67. vrchatapi/models/avatar_unity_package_url_object.py +1 -1
  68. vrchatapi/models/badge.py +1 -1
  69. vrchatapi/models/balance.py +1 -1
  70. vrchatapi/models/ban_group_member_request.py +1 -1
  71. vrchatapi/models/bare_error.py +1 -1
  72. vrchatapi/models/beta.py +1 -1
  73. vrchatapi/models/beta_registration_not_found_error.py +1 -1
  74. vrchatapi/models/beta_user_field.py +1 -1
  75. vrchatapi/models/boop_request.py +1 -1
  76. vrchatapi/models/calendar_day_of_week.py +1 -1
  77. vrchatapi/models/calendar_event.py +1 -1
  78. vrchatapi/models/calendar_event_access.py +1 -1
  79. vrchatapi/models/calendar_event_category.py +1 -1
  80. vrchatapi/models/calendar_event_discovery.py +1 -1
  81. vrchatapi/models/calendar_event_discovery_inclusion.py +1 -1
  82. vrchatapi/models/calendar_event_discovery_scope.py +1 -1
  83. vrchatapi/models/calendar_event_frequency.py +1 -1
  84. vrchatapi/models/calendar_event_occurrence_kind.py +1 -1
  85. vrchatapi/models/calendar_event_platform.py +1 -1
  86. vrchatapi/models/calendar_event_recurrence.py +1 -1
  87. vrchatapi/models/calendar_event_recurrence_end.py +1 -1
  88. vrchatapi/models/calendar_event_recurrence_end_type.py +1 -1
  89. vrchatapi/models/calendar_event_user_interest.py +1 -1
  90. vrchatapi/models/change_user_tags_request.py +1 -1
  91. vrchatapi/models/change_world_tags_request.py +1 -1
  92. vrchatapi/models/content_filter.py +1 -1
  93. vrchatapi/models/create_avatar_moderation_request.py +1 -1
  94. vrchatapi/models/create_avatar_request.py +1 -1
  95. vrchatapi/models/create_avatar_request_release_status.py +1 -1
  96. vrchatapi/models/create_calendar_event_request.py +1 -1
  97. vrchatapi/models/create_file_request.py +1 -1
  98. vrchatapi/models/create_file_request_mime_type.py +1 -1
  99. vrchatapi/models/create_file_version_request.py +1 -1
  100. vrchatapi/models/create_group_announcement_request.py +1 -1
  101. vrchatapi/models/create_group_gallery_request.py +1 -1
  102. vrchatapi/models/create_group_invite_request.py +1 -1
  103. vrchatapi/models/create_group_post_request.py +1 -1
  104. vrchatapi/models/create_group_request.py +1 -1
  105. vrchatapi/models/create_group_role_request.py +1 -1
  106. vrchatapi/models/create_instance_request.py +1 -1
  107. vrchatapi/models/create_instance_request_region.py +1 -1
  108. vrchatapi/models/create_jam_submission_request.py +1 -1
  109. vrchatapi/models/create_listing_request.py +1 -1
  110. vrchatapi/models/create_product_request.py +1 -1
  111. vrchatapi/models/create_product_request_type.py +1 -1
  112. vrchatapi/models/create_prop_request.py +1 -1
  113. vrchatapi/models/create_world_request.py +1 -1
  114. vrchatapi/models/create_world_request_release_status.py +1 -1
  115. vrchatapi/models/current_user.py +1 -1
  116. vrchatapi/models/current_user_login_response.py +1 -1
  117. vrchatapi/models/current_user_presence.py +1 -1
  118. vrchatapi/models/decline_group_invite_request.py +1 -1
  119. vrchatapi/models/developer_type.py +1 -1
  120. vrchatapi/models/disable2_fa_result.py +1 -1
  121. vrchatapi/models/discord_details.py +1 -1
  122. vrchatapi/models/dynamic_content_row.py +1 -1
  123. vrchatapi/models/earnings_metrics.py +1 -1
  124. vrchatapi/models/earnings_metrics_totals.py +1 -1
  125. vrchatapi/models/economy_account.py +1 -1
  126. vrchatapi/models/economy_account_limits.py +1 -1
  127. vrchatapi/models/economy_balances.py +1 -1
  128. vrchatapi/models/economy_payout.py +1 -1
  129. vrchatapi/models/economy_payout_eligibility.py +1 -1
  130. vrchatapi/models/economy_payout_list.py +1 -1
  131. vrchatapi/models/economy_payout_status.py +1 -1
  132. vrchatapi/models/economy_status.py +1 -1
  133. vrchatapi/models/equip_inventory_item_request.py +1 -1
  134. vrchatapi/models/error.py +1 -1
  135. vrchatapi/models/favorite.py +1 -1
  136. vrchatapi/models/favorite_group.py +1 -1
  137. vrchatapi/models/favorite_group_contents.py +1 -1
  138. vrchatapi/models/favorite_group_contents_entry.py +1 -1
  139. vrchatapi/models/favorite_group_contents_entry_world.py +1 -1
  140. vrchatapi/models/favorite_group_limits.py +1 -1
  141. vrchatapi/models/favorite_group_list.py +1 -1
  142. vrchatapi/models/favorite_group_summary.py +1 -1
  143. vrchatapi/models/favorite_group_visibility.py +1 -1
  144. vrchatapi/models/favorite_limits.py +1 -1
  145. vrchatapi/models/favorite_type.py +1 -1
  146. vrchatapi/models/favorited_world.py +1 -1
  147. vrchatapi/models/feedback.py +1 -1
  148. vrchatapi/models/file.py +1 -1
  149. vrchatapi/models/file_analysis.py +1 -1
  150. vrchatapi/models/file_analysis_avatar_stats.py +1 -1
  151. vrchatapi/models/file_data.py +1 -1
  152. vrchatapi/models/file_status.py +1 -1
  153. vrchatapi/models/file_upload_url.py +1 -1
  154. vrchatapi/models/file_version.py +1 -1
  155. vrchatapi/models/file_version_upload_status.py +1 -1
  156. vrchatapi/models/finish_file_data_upload_request.py +1 -1
  157. vrchatapi/models/follow_calendar_event_request.py +1 -1
  158. vrchatapi/models/friend_status.py +1 -1
  159. vrchatapi/models/group.py +1 -1
  160. vrchatapi/models/group_access_type.py +1 -1
  161. vrchatapi/models/group_announcement.py +1 -1
  162. vrchatapi/models/group_audit_log_entry.py +1 -1
  163. vrchatapi/models/group_audit_log_entry_base.py +1 -1
  164. vrchatapi/models/group_audit_log_entry_boolean_change.py +1 -1
  165. vrchatapi/models/group_audit_log_entry_data.py +1 -1
  166. vrchatapi/models/group_audit_log_entry_data_group_announcement.py +1 -1
  167. vrchatapi/models/group_audit_log_entry_data_group_calendar_event_create.py +1 -1
  168. vrchatapi/models/group_audit_log_entry_data_group_calendar_event_delete.py +1 -1
  169. vrchatapi/models/group_audit_log_entry_data_group_gallery_create.py +1 -1
  170. vrchatapi/models/group_audit_log_entry_data_group_gallery_delete.py +1 -1
  171. vrchatapi/models/group_audit_log_entry_data_group_gallery_update.py +1 -1
  172. vrchatapi/models/group_audit_log_entry_data_group_instance_announcement.py +1 -1
  173. vrchatapi/models/group_audit_log_entry_data_group_instance_close.py +1 -1
  174. vrchatapi/models/group_audit_log_entry_data_group_instance_create.py +1 -1
  175. vrchatapi/models/group_audit_log_entry_data_group_instance_moderation.py +1 -1
  176. vrchatapi/models/group_audit_log_entry_data_group_member_role.py +1 -1
  177. vrchatapi/models/group_audit_log_entry_data_group_member_user_update.py +1 -1
  178. vrchatapi/models/group_audit_log_entry_data_group_post.py +1 -1
  179. vrchatapi/models/group_audit_log_entry_data_group_post_create.py +1 -1
  180. vrchatapi/models/group_audit_log_entry_data_group_post_delete.py +1 -1
  181. vrchatapi/models/group_audit_log_entry_data_group_post_update.py +1 -1
  182. vrchatapi/models/group_audit_log_entry_data_group_role.py +1 -1
  183. vrchatapi/models/group_audit_log_entry_data_group_role_create.py +1 -1
  184. vrchatapi/models/group_audit_log_entry_data_group_role_delete.py +1 -1
  185. vrchatapi/models/group_audit_log_entry_data_group_role_update.py +1 -1
  186. vrchatapi/models/group_audit_log_entry_data_group_update.py +1 -1
  187. vrchatapi/models/group_audit_log_entry_file_id_change.py +1 -1
  188. vrchatapi/models/group_audit_log_entry_group_announcement.py +1 -1
  189. vrchatapi/models/group_audit_log_entry_group_calendar_event_create.py +1 -1
  190. vrchatapi/models/group_audit_log_entry_group_calendar_event_delete.py +1 -1
  191. vrchatapi/models/group_audit_log_entry_group_gallery_create.py +1 -1
  192. vrchatapi/models/group_audit_log_entry_group_gallery_delete.py +1 -1
  193. vrchatapi/models/group_audit_log_entry_group_gallery_update.py +1 -1
  194. vrchatapi/models/group_audit_log_entry_group_instance_announcement.py +1 -1
  195. vrchatapi/models/group_audit_log_entry_group_instance_close.py +1 -1
  196. vrchatapi/models/group_audit_log_entry_group_instance_create.py +1 -1
  197. vrchatapi/models/group_audit_log_entry_group_instance_kick.py +1 -1
  198. vrchatapi/models/group_audit_log_entry_group_instance_warn.py +1 -1
  199. vrchatapi/models/group_audit_log_entry_group_invite_cancel.py +1 -1
  200. vrchatapi/models/group_audit_log_entry_group_invite_create.py +1 -1
  201. vrchatapi/models/group_audit_log_entry_group_member_join.py +1 -1
  202. vrchatapi/models/group_audit_log_entry_group_member_leave.py +1 -1
  203. vrchatapi/models/group_audit_log_entry_group_member_remove.py +1 -1
  204. vrchatapi/models/group_audit_log_entry_group_member_role_assign.py +1 -1
  205. vrchatapi/models/group_audit_log_entry_group_member_role_unassign.py +1 -1
  206. vrchatapi/models/group_audit_log_entry_group_member_user_update.py +1 -1
  207. vrchatapi/models/group_audit_log_entry_group_post_create.py +1 -1
  208. vrchatapi/models/group_audit_log_entry_group_post_delete.py +1 -1
  209. vrchatapi/models/group_audit_log_entry_group_post_update.py +1 -1
  210. vrchatapi/models/group_audit_log_entry_group_request_block.py +1 -1
  211. vrchatapi/models/group_audit_log_entry_group_request_create.py +1 -1
  212. vrchatapi/models/group_audit_log_entry_group_request_reject.py +1 -1
  213. vrchatapi/models/group_audit_log_entry_group_request_withdraw.py +1 -1
  214. vrchatapi/models/group_audit_log_entry_group_role_create.py +1 -1
  215. vrchatapi/models/group_audit_log_entry_group_role_delete.py +1 -1
  216. vrchatapi/models/group_audit_log_entry_group_role_update.py +1 -1
  217. vrchatapi/models/group_audit_log_entry_group_update.py +1 -1
  218. vrchatapi/models/group_audit_log_entry_group_user_ban.py +1 -1
  219. vrchatapi/models/group_audit_log_entry_group_user_unban.py +1 -1
  220. vrchatapi/models/group_audit_log_entry_integer_change.py +1 -1
  221. vrchatapi/models/group_audit_log_entry_join_state_change.py +1 -1
  222. vrchatapi/models/group_audit_log_entry_string_change.py +1 -1
  223. vrchatapi/models/group_audit_log_entry_string_list_change.py +1 -1
  224. vrchatapi/models/group_audit_log_entry_unknown.py +1 -1
  225. vrchatapi/models/group_audit_log_entry_user_id_change.py +1 -1
  226. vrchatapi/models/group_gallery.py +1 -1
  227. vrchatapi/models/group_gallery_file_order.py +1 -1
  228. vrchatapi/models/group_gallery_file_order_request.py +1 -1
  229. vrchatapi/models/group_gallery_image.py +1 -1
  230. vrchatapi/models/group_gallery_image_list.py +1 -1
  231. vrchatapi/models/group_instance.py +1 -1
  232. vrchatapi/models/group_join_request_action.py +1 -1
  233. vrchatapi/models/group_join_state.py +1 -1
  234. vrchatapi/models/group_member.py +1 -1
  235. vrchatapi/models/group_member_limited_user.py +1 -1
  236. vrchatapi/models/group_member_search_response.py +1 -1
  237. vrchatapi/models/group_member_status.py +1 -1
  238. vrchatapi/models/group_my_member.py +1 -1
  239. vrchatapi/models/group_permission.py +1 -1
  240. vrchatapi/models/group_permissions.py +1 -1
  241. vrchatapi/models/group_post.py +1 -1
  242. vrchatapi/models/group_post_visibility.py +1 -1
  243. vrchatapi/models/group_posts_response.py +1 -1
  244. vrchatapi/models/group_privacy.py +1 -1
  245. vrchatapi/models/group_role.py +1 -1
  246. vrchatapi/models/group_role_template.py +1 -1
  247. vrchatapi/models/group_role_template_role.py +1 -1
  248. vrchatapi/models/group_role_template_values.py +1 -1
  249. vrchatapi/models/group_search_sort.py +1 -1
  250. vrchatapi/models/group_transferable.py +1 -1
  251. vrchatapi/models/group_transferable_requirements.py +1 -1
  252. vrchatapi/models/group_user_visibility.py +1 -1
  253. vrchatapi/models/image_animation_style.py +1 -1
  254. vrchatapi/models/image_loop_style.py +1 -1
  255. vrchatapi/models/image_mask.py +1 -1
  256. vrchatapi/models/info_push.py +1 -1
  257. vrchatapi/models/info_push_data.py +1 -1
  258. vrchatapi/models/info_push_data_article.py +1 -1
  259. vrchatapi/models/info_push_data_article_content.py +1 -1
  260. vrchatapi/models/info_push_data_call_to_action.py +1 -1
  261. vrchatapi/models/info_push_data_category.py +1 -1
  262. vrchatapi/models/info_push_data_clickable.py +1 -1
  263. vrchatapi/models/info_push_data_content_source.py +1 -1
  264. vrchatapi/models/info_push_data_content_source_pagination.py +1 -1
  265. vrchatapi/models/info_push_data_control.py +1 -1
  266. vrchatapi/models/info_push_data_control_option.py +1 -1
  267. vrchatapi/models/info_push_data_delivery_behavior.py +1 -1
  268. vrchatapi/models/info_push_data_domain_list_inner.py +1 -1
  269. vrchatapi/models/info_push_data_presentation.py +1 -1
  270. vrchatapi/models/info_push_data_promotion.py +1 -1
  271. vrchatapi/models/info_push_data_promotion_notification.py +1 -1
  272. vrchatapi/models/info_push_data_search.py +1 -1
  273. vrchatapi/models/info_push_embedded_link.py +1 -1
  274. vrchatapi/models/info_push_experiment.py +1 -1
  275. vrchatapi/models/info_push_ips_query.py +1 -1
  276. vrchatapi/models/instance.py +1 -1
  277. vrchatapi/models/instance_category.py +1 -1
  278. vrchatapi/models/instance_content_settings.py +1 -1
  279. vrchatapi/models/instance_platforms.py +1 -1
  280. vrchatapi/models/instance_region.py +1 -1
  281. vrchatapi/models/instance_short_name_response.py +1 -1
  282. vrchatapi/models/instance_type.py +1 -1
  283. vrchatapi/models/instance_vibe.py +1 -1
  284. vrchatapi/models/interests_and_preferences.py +1 -1
  285. vrchatapi/models/inventory.py +1 -1
  286. vrchatapi/models/inventory_asset.py +1 -1
  287. vrchatapi/models/inventory_consumption_results.py +1 -1
  288. vrchatapi/models/inventory_default_attributes1.py +1 -1
  289. vrchatapi/models/inventory_default_attributes1_validator.py +1 -1
  290. vrchatapi/models/inventory_drop.py +1 -1
  291. vrchatapi/models/inventory_equip_slot.py +1 -1
  292. vrchatapi/models/inventory_flag.py +1 -1
  293. vrchatapi/models/inventory_item.py +1 -1
  294. vrchatapi/models/inventory_item_type.py +1 -1
  295. vrchatapi/models/inventory_metadata.py +1 -1
  296. vrchatapi/models/inventory_notification_details.py +1 -1
  297. vrchatapi/models/inventory_sort_order.py +1 -1
  298. vrchatapi/models/inventory_spawn.py +1 -1
  299. vrchatapi/models/inventory_template.py +1 -1
  300. vrchatapi/models/inventory_user_attributes.py +1 -1
  301. vrchatapi/models/invite_message.py +1 -1
  302. vrchatapi/models/invite_message_type.py +1 -1
  303. vrchatapi/models/invite_request.py +1 -1
  304. vrchatapi/models/invite_response.py +1 -1
  305. vrchatapi/models/jam.py +1 -1
  306. vrchatapi/models/jam_state_change_dates.py +1 -1
  307. vrchatapi/models/jam_submission.py +1 -1
  308. vrchatapi/models/join_group_request.py +1 -1
  309. vrchatapi/models/license.py +1 -1
  310. vrchatapi/models/license_action.py +1 -1
  311. vrchatapi/models/license_group.py +1 -1
  312. vrchatapi/models/license_type.py +1 -1
  313. vrchatapi/models/limited_group.py +1 -1
  314. vrchatapi/models/limited_unity_package.py +1 -1
  315. vrchatapi/models/limited_user_friend.py +1 -1
  316. vrchatapi/models/limited_user_groups.py +1 -1
  317. vrchatapi/models/limited_user_instance.py +1 -1
  318. vrchatapi/models/limited_user_search.py +1 -1
  319. vrchatapi/models/limited_world.py +1 -1
  320. vrchatapi/models/localized_string.py +1 -1
  321. vrchatapi/models/mime_type.py +1 -1
  322. vrchatapi/models/model_print.py +1 -1
  323. vrchatapi/models/moderate_user_request.py +1 -1
  324. vrchatapi/models/moderation_report.py +1 -1
  325. vrchatapi/models/mutual_friend.py +1 -1
  326. vrchatapi/models/mutuals.py +1 -1
  327. vrchatapi/models/notification.py +1 -1
  328. vrchatapi/models/notification_base.py +1 -1
  329. vrchatapi/models/notification_boop.py +1 -1
  330. vrchatapi/models/notification_detail_boop.py +1 -1
  331. vrchatapi/models/notification_detail_invite.py +1 -1
  332. vrchatapi/models/notification_detail_invite_response.py +1 -1
  333. vrchatapi/models/notification_detail_request_invite.py +1 -1
  334. vrchatapi/models/notification_detail_request_invite_response.py +1 -1
  335. vrchatapi/models/notification_detail_vote_to_kick.py +1 -1
  336. vrchatapi/models/notification_friend_request.py +1 -1
  337. vrchatapi/models/notification_invite.py +1 -1
  338. vrchatapi/models/notification_invite_response.py +1 -1
  339. vrchatapi/models/notification_message.py +1 -1
  340. vrchatapi/models/notification_request_invite.py +1 -1
  341. vrchatapi/models/notification_request_invite_response.py +1 -1
  342. vrchatapi/models/notification_type.py +1 -1
  343. vrchatapi/models/notification_unknown.py +1 -1
  344. vrchatapi/models/notification_v2.py +1 -1
  345. vrchatapi/models/notification_v2_data.py +1 -1
  346. vrchatapi/models/notification_v2_data_badge_earned.py +1 -1
  347. vrchatapi/models/notification_v2_data_boop.py +1 -1
  348. vrchatapi/models/notification_v2_data_event_announcement.py +1 -1
  349. vrchatapi/models/notification_v2_data_group_announcement.py +1 -1
  350. vrchatapi/models/notification_v2_data_group_informative.py +1 -1
  351. vrchatapi/models/notification_v2_data_group_transfer.py +1 -1
  352. vrchatapi/models/notification_v2_details_boop.py +1 -1
  353. vrchatapi/models/notification_v2_response.py +1 -1
  354. vrchatapi/models/notification_v2_type.py +1 -1
  355. vrchatapi/models/notification_vote_to_kick.py +1 -1
  356. vrchatapi/models/o_auth_redirect_code.py +1 -1
  357. vrchatapi/models/ok_status.py +1 -1
  358. vrchatapi/models/ok_status2.py +1 -1
  359. vrchatapi/models/order_option.py +1 -1
  360. vrchatapi/models/order_option_short.py +1 -1
  361. vrchatapi/models/paginated_calendar_event_list.py +1 -1
  362. vrchatapi/models/paginated_group_audit_log_entry_list.py +1 -1
  363. vrchatapi/models/paginated_moderation_report_list.py +1 -1
  364. vrchatapi/models/past_display_name.py +1 -1
  365. vrchatapi/models/pending2_fa_result.py +1 -1
  366. vrchatapi/models/performance_limiter_info.py +1 -1
  367. vrchatapi/models/performance_ratings.py +1 -1
  368. vrchatapi/models/permission.py +1 -1
  369. vrchatapi/models/permission_data.py +1 -1
  370. vrchatapi/models/platform_build_info.py +1 -1
  371. vrchatapi/models/platform_history_entry.py +1 -1
  372. vrchatapi/models/player_moderation.py +1 -1
  373. vrchatapi/models/player_moderation_type.py +1 -1
  374. vrchatapi/models/print_files.py +1 -1
  375. vrchatapi/models/private_profile.py +1 -1
  376. vrchatapi/models/private_profile_activity.py +1 -1
  377. vrchatapi/models/product.py +1 -1
  378. vrchatapi/models/product_listing.py +1 -1
  379. vrchatapi/models/product_listing_attribution.py +1 -1
  380. vrchatapi/models/product_listing_attribution_creator.py +1 -1
  381. vrchatapi/models/product_listing_type.py +1 -1
  382. vrchatapi/models/product_listing_variant.py +1 -1
  383. vrchatapi/models/product_purchase.py +1 -1
  384. vrchatapi/models/product_purchase_history.py +1 -1
  385. vrchatapi/models/product_purchase_location_type.py +1 -1
  386. vrchatapi/models/product_purchase_product.py +1 -1
  387. vrchatapi/models/product_purchase_purchase_context.py +1 -1
  388. vrchatapi/models/product_purchase_record.py +1 -1
  389. vrchatapi/models/product_type.py +1 -1
  390. vrchatapi/models/profile_group.py +1 -1
  391. vrchatapi/models/profile_groups.py +1 -1
  392. vrchatapi/models/profile_represented_group.py +1 -1
  393. vrchatapi/models/prop.py +1 -1
  394. vrchatapi/models/prop_publish_status.py +1 -1
  395. vrchatapi/models/prop_unity_package.py +1 -1
  396. vrchatapi/models/public_profile.py +1 -1
  397. vrchatapi/models/purchase_context_data.py +1 -1
  398. vrchatapi/models/purchase_product_listing_request.py +1 -1
  399. vrchatapi/models/region.py +1 -1
  400. vrchatapi/models/register_user_account_request.py +1 -1
  401. vrchatapi/models/release_status.py +1 -1
  402. vrchatapi/models/report_category.py +1 -1
  403. vrchatapi/models/report_reason.py +1 -1
  404. vrchatapi/models/represented_group.py +1 -1
  405. vrchatapi/models/request_invite_request.py +1 -1
  406. vrchatapi/models/requires_two_factor_auth.py +1 -1
  407. vrchatapi/models/respond_group_join_request.py +1 -1
  408. vrchatapi/models/respond_notification_v2_request.py +1 -1
  409. vrchatapi/models/response.py +1 -1
  410. vrchatapi/models/reward_badge.py +1 -1
  411. vrchatapi/models/reward_redemption.py +1 -1
  412. vrchatapi/models/reward_redemption_data.py +1 -1
  413. vrchatapi/models/reward_redemption_request.py +1 -1
  414. vrchatapi/models/reward_redemption_result.py +1 -1
  415. vrchatapi/models/route_not_implemented.py +1 -1
  416. vrchatapi/models/seller_eligibility.py +1 -1
  417. vrchatapi/models/sent_notification.py +1 -1
  418. vrchatapi/models/sent_notification_details.py +1 -1
  419. vrchatapi/models/service_queue_stats.py +1 -1
  420. vrchatapi/models/service_status.py +1 -1
  421. vrchatapi/models/share_inventory_item_direct_request.py +1 -1
  422. vrchatapi/models/sort_option.py +1 -1
  423. vrchatapi/models/sort_option_avatar.py +1 -1
  424. vrchatapi/models/sort_option_product_purchase.py +1 -1
  425. vrchatapi/models/sso_provider.py +1 -1
  426. vrchatapi/models/sso_token.py +1 -1
  427. vrchatapi/models/store.py +1 -1
  428. vrchatapi/models/store_context.py +1 -1
  429. vrchatapi/models/store_shelf.py +1 -1
  430. vrchatapi/models/store_type.py +1 -1
  431. vrchatapi/models/store_view.py +1 -1
  432. vrchatapi/models/submit_moderation_report_request.py +1 -1
  433. vrchatapi/models/submit_moderation_report_request_details.py +1 -1
  434. vrchatapi/models/subscription.py +1 -1
  435. vrchatapi/models/subscription_period.py +1 -1
  436. vrchatapi/models/success.py +1 -1
  437. vrchatapi/models/success_flag.py +1 -1
  438. vrchatapi/models/tilia_kyc.py +1 -1
  439. vrchatapi/models/tilia_status.py +1 -1
  440. vrchatapi/models/tilia_tos.py +1 -1
  441. vrchatapi/models/token_bundle.py +1 -1
  442. vrchatapi/models/transaction.py +1 -1
  443. vrchatapi/models/transaction_agreement.py +1 -1
  444. vrchatapi/models/transaction_status.py +1 -1
  445. vrchatapi/models/transaction_steam_info.py +1 -1
  446. vrchatapi/models/transaction_steam_wallet_info.py +1 -1
  447. vrchatapi/models/transfer_group_request.py +1 -1
  448. vrchatapi/models/tutorial_status.py +1 -1
  449. vrchatapi/models/two_factor_auth_code.py +1 -1
  450. vrchatapi/models/two_factor_auth_type.py +1 -1
  451. vrchatapi/models/two_factor_email_code.py +1 -1
  452. vrchatapi/models/two_factor_recovery_codes.py +1 -1
  453. vrchatapi/models/two_factor_recovery_codes_otp_inner.py +1 -1
  454. vrchatapi/models/unavailable_world.py +1 -1
  455. vrchatapi/models/unity_package.py +1 -1
  456. vrchatapi/models/update_asset_review_notes_request.py +1 -1
  457. vrchatapi/models/update_avatar_request.py +1 -1
  458. vrchatapi/models/update_avatar_request_release_status.py +1 -1
  459. vrchatapi/models/update_calendar_event_request.py +1 -1
  460. vrchatapi/models/update_favorite_group_request.py +1 -1
  461. vrchatapi/models/update_group_gallery_request.py +1 -1
  462. vrchatapi/models/update_group_member_request.py +1 -1
  463. vrchatapi/models/update_group_representation_request.py +1 -1
  464. vrchatapi/models/update_group_request.py +1 -1
  465. vrchatapi/models/update_group_role_request.py +1 -1
  466. vrchatapi/models/update_instance_request.py +1 -1
  467. vrchatapi/models/update_inventory_item_request.py +1 -1
  468. vrchatapi/models/update_invite_message_request.py +1 -1
  469. vrchatapi/models/update_listing_request.py +1 -1
  470. vrchatapi/models/update_product_request.py +1 -1
  471. vrchatapi/models/update_profile_request.py +1 -1
  472. vrchatapi/models/update_prop_request.py +1 -1
  473. vrchatapi/models/update_tilia_tos_request.py +1 -1
  474. vrchatapi/models/update_user_badge_request.py +1 -1
  475. vrchatapi/models/update_user_client_config_request.py +1 -1
  476. vrchatapi/models/update_user_note_request.py +1 -1
  477. vrchatapi/models/update_user_request.py +1 -1
  478. vrchatapi/models/update_world_request.py +1 -1
  479. vrchatapi/models/user.py +1 -1
  480. vrchatapi/models/user_client_config.py +1 -1
  481. vrchatapi/models/user_cosmetic.py +1 -1
  482. vrchatapi/models/user_credits_eligible.py +1 -1
  483. vrchatapi/models/user_exists.py +1 -1
  484. vrchatapi/models/user_group_instance_list_response.py +1 -1
  485. vrchatapi/models/user_note.py +1 -1
  486. vrchatapi/models/user_note_target_user.py +1 -1
  487. vrchatapi/models/user_response.py +1 -1
  488. vrchatapi/models/user_search_sort.py +1 -1
  489. vrchatapi/models/user_state.py +1 -1
  490. vrchatapi/models/user_status.py +1 -1
  491. vrchatapi/models/user_subscription.py +1 -1
  492. vrchatapi/models/user_subscription_eligible.py +1 -1
  493. vrchatapi/models/verify2_fa_email_code_result.py +1 -1
  494. vrchatapi/models/verify2_fa_result.py +1 -1
  495. vrchatapi/models/verify_auth_token_result.py +1 -1
  496. vrchatapi/models/websocket_clear_notification.py +1 -1
  497. vrchatapi/models/websocket_content_refresh.py +1 -1
  498. vrchatapi/models/websocket_content_refresh_action_type.py +1 -1
  499. vrchatapi/models/websocket_content_refresh_encoded.py +1 -1
  500. vrchatapi/models/websocket_friend_active.py +1 -1
  501. vrchatapi/models/websocket_friend_active_encoded.py +1 -1
  502. vrchatapi/models/websocket_friend_add.py +1 -1
  503. vrchatapi/models/websocket_friend_add_encoded.py +1 -1
  504. vrchatapi/models/websocket_friend_delete.py +1 -1
  505. vrchatapi/models/websocket_friend_delete_encoded.py +1 -1
  506. vrchatapi/models/websocket_friend_location.py +1 -1
  507. vrchatapi/models/websocket_friend_location_encoded.py +1 -1
  508. vrchatapi/models/websocket_friend_offline.py +1 -1
  509. vrchatapi/models/websocket_friend_offline_encoded.py +1 -1
  510. vrchatapi/models/websocket_friend_online.py +1 -1
  511. vrchatapi/models/websocket_friend_online_encoded.py +1 -1
  512. vrchatapi/models/websocket_friend_update.py +1 -1
  513. vrchatapi/models/websocket_friend_update_encoded.py +1 -1
  514. vrchatapi/models/websocket_group_joined.py +1 -1
  515. vrchatapi/models/websocket_group_joined_encoded.py +1 -1
  516. vrchatapi/models/websocket_group_left.py +1 -1
  517. vrchatapi/models/websocket_group_left_encoded.py +1 -1
  518. vrchatapi/models/websocket_group_member_updated.py +1 -1
  519. vrchatapi/models/websocket_group_member_updated_encoded.py +1 -1
  520. vrchatapi/models/websocket_group_role_updated.py +1 -1
  521. vrchatapi/models/websocket_group_role_updated_encoded.py +1 -1
  522. vrchatapi/models/websocket_hide_notification.py +1 -1
  523. vrchatapi/models/websocket_instance_queue_joined.py +1 -1
  524. vrchatapi/models/websocket_instance_queue_joined_encoded.py +1 -1
  525. vrchatapi/models/websocket_instance_queue_ready.py +1 -1
  526. vrchatapi/models/websocket_instance_queue_ready_encoded.py +1 -1
  527. vrchatapi/models/websocket_message.py +1 -1
  528. vrchatapi/models/websocket_message_unknown.py +1 -1
  529. vrchatapi/models/websocket_notification.py +1 -1
  530. vrchatapi/models/websocket_notification_detail_boop.py +1 -1
  531. vrchatapi/models/websocket_notification_detail_invite.py +1 -1
  532. vrchatapi/models/websocket_notification_detail_invite_response.py +1 -1
  533. vrchatapi/models/websocket_notification_detail_request_invite.py +1 -1
  534. vrchatapi/models/websocket_notification_detail_request_invite_response.py +1 -1
  535. vrchatapi/models/websocket_notification_detail_vote_to_kick.py +1 -1
  536. vrchatapi/models/websocket_notification_encoded.py +1 -1
  537. vrchatapi/models/websocket_notification_unknown.py +1 -1
  538. vrchatapi/models/websocket_notification_v2_delete.py +1 -1
  539. vrchatapi/models/websocket_notification_v2_delete_encoded.py +1 -1
  540. vrchatapi/models/websocket_notification_v2_encoded.py +1 -1
  541. vrchatapi/models/websocket_notification_v2_update.py +1 -1
  542. vrchatapi/models/websocket_notification_v2_update_encoded.py +1 -1
  543. vrchatapi/models/websocket_response_notification.py +1 -1
  544. vrchatapi/models/websocket_response_notification_encoded.py +1 -1
  545. vrchatapi/models/websocket_see_notification.py +1 -1
  546. vrchatapi/models/websocket_user_badge_assigned.py +1 -1
  547. vrchatapi/models/websocket_user_badge_assigned_encoded.py +1 -1
  548. vrchatapi/models/websocket_user_badge_unassigned.py +1 -1
  549. vrchatapi/models/websocket_user_badge_unassigned_encoded.py +1 -1
  550. vrchatapi/models/websocket_user_location.py +1 -1
  551. vrchatapi/models/websocket_user_location_encoded.py +1 -1
  552. vrchatapi/models/websocket_user_update.py +1 -1
  553. vrchatapi/models/websocket_user_update_encoded.py +1 -1
  554. vrchatapi/models/world.py +1 -1
  555. vrchatapi/models/world_favorite_list.py +1 -1
  556. vrchatapi/models/world_metadata.py +1 -1
  557. vrchatapi/models/world_publish_status.py +1 -1
  558. vrchatapi/rest.py +1 -1
  559. {vrchatapi-1.22.2.dev5.dist-info → vrchatapi-1.22.2.dev6.dist-info}/METADATA +1 -1
  560. vrchatapi-1.22.2.dev6.dist-info/RECORD +564 -0
  561. vrchatapi-1.22.2.dev5.dist-info/RECORD +0 -564
  562. {vrchatapi-1.22.2.dev5.dist-info → vrchatapi-1.22.2.dev6.dist-info}/WHEEL +0 -0
  563. {vrchatapi-1.22.2.dev5.dist-info → vrchatapi-1.22.2.dev6.dist-info}/licenses/LICENSE +0 -0
  564. {vrchatapi-1.22.2.dev5.dist-info → vrchatapi-1.22.2.dev6.dist-info}/top_level.txt +0 -0
vrchatapi/__init__.py CHANGED
@@ -7,7 +7,7 @@
7
7
 
8
8
  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
9
9
 
10
- The version of the OpenAPI document: 1.22.2-nightly.5
10
+ The version of the OpenAPI document: 1.22.2-nightly.6
11
11
  Generated by: https://openapi-generator.tech
12
12
  """
13
13
 
vrchatapi/api/authentication_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/avatars_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/calendar_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/economy_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/favorites_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/files_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/friends_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/groups_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/instances_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/inventory_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/invite_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/jams_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/miscellaneous_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/notifications_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/playermoderation_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/prints_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/props_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api/users_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
@@ -2637,7 +2637,7 @@ class UsersApi(object):
2637
2637
  def get_user_feedback(self, user_id, **kwargs): # noqa: E501
2638
2638
  """Get User Feedback # noqa: E501
2639
2639
 
2640
- Get user's submitted feedback # noqa: E501
2640
+ Get user's submitted feedback. VRChat staff note that [moderation reports](https://vrchat.community/reference/get-moderation-reports) replace the feedback system in [Feedback deprecated](https://github.com/vrchatapi/specification/issues/535), December 5, 2025. # noqa: E501
2641
2641
  This method makes a synchronous HTTP request by default. To make an
2642
2642
  asynchronous HTTP request, please pass async_req=True
2643
2643
 
@@ -2673,7 +2673,7 @@ class UsersApi(object):
2673
2673
  def get_user_feedback_with_http_info(self, user_id, **kwargs): # noqa: E501
2674
2674
  """Get User Feedback # noqa: E501
2675
2675
 
2676
- Get user's submitted feedback # noqa: E501
2676
+ Get user's submitted feedback. VRChat staff note that [moderation reports](https://vrchat.community/reference/get-moderation-reports) replace the feedback system in [Feedback deprecated](https://github.com/vrchatapi/specification/issues/535), December 5, 2025. # noqa: E501
2677
2677
  This method makes a synchronous HTTP request by default. To make an
2678
2678
  asynchronous HTTP request, please pass async_req=True
2679
2679
 
vrchatapi/api/worlds_api.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/api_client.py CHANGED
@@ -4,7 +4,7 @@
4
4
 
5
5
  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
6
6
 
7
- The version of the OpenAPI document: 1.22.2-nightly.5
7
+ The version of the OpenAPI document: 1.22.2-nightly.6
8
8
  Generated by: https://openapi-generator.tech
9
9
  """
10
10
 
vrchatapi/configuration.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
@@ -447,7 +447,7 @@ conf = vrchatapi.Configuration(
447
447
  return "Python SDK Debug Report:\n"\
448
448
  "OS: {env}\n"\
449
449
  "Python Version: {pyversion}\n"\
450
- "Version of the API: 1.22.2-nightly.5\n"\
450
+ "Version of the API: 1.22.2-nightly.6\n"\
451
451
  "SDK Package Version: 1.0.0".\
452
452
  format(env=sys.platform, pyversion=sys.version)
453
453
 
vrchatapi/exceptions.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/__init__.py CHANGED
@@ -6,7 +6,7 @@
6
6
 
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
8
8
 
9
- The version of the OpenAPI document: 1.22.2-nightly.5
9
+ The version of the OpenAPI document: 1.22.2-nightly.6
10
10
  Generated by: https://openapi-generator.tech
11
11
  """
12
12
 
vrchatapi/models/account_deletion_log.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/add_favorite_request.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/add_group_gallery_image_request.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/admin_asset_bundle.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/admin_unity_package.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/age_verification_status.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/age_verification_status_result.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/agreement.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/agreement_code.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/agreement_request.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/agreement_status.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
vrchatapi/models/api_config.py CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  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
7
7
 
8
- The version of the OpenAPI document: 1.22.2-nightly.5
8
+ The version of the OpenAPI document: 1.22.2-nightly.6
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11