vrchatapi 1.21.1.dev84__py3-none-any.whl → 1.22.1.dev1__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 (487) hide show
  1. vrchatapi/__init__.py +2 -3
  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 +1 -1
  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 +2 -3
  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_calendar_event_request.py +1 -1
  96. vrchatapi/models/create_file_request.py +1 -1
  97. vrchatapi/models/create_file_version_request.py +1 -1
  98. vrchatapi/models/create_group_announcement_request.py +1 -1
  99. vrchatapi/models/create_group_gallery_request.py +1 -1
  100. vrchatapi/models/create_group_invite_request.py +1 -1
  101. vrchatapi/models/create_group_post_request.py +1 -1
  102. vrchatapi/models/create_group_request.py +1 -1
  103. vrchatapi/models/create_group_role_request.py +1 -1
  104. vrchatapi/models/create_instance_request.py +1 -1
  105. vrchatapi/models/create_jam_submission_request.py +1 -1
  106. vrchatapi/models/create_listing_request.py +1 -1
  107. vrchatapi/models/create_product_request.py +1 -1
  108. vrchatapi/models/create_prop_request.py +1 -1
  109. vrchatapi/models/create_world_request.py +1 -1
  110. vrchatapi/models/current_user.py +1 -1
  111. vrchatapi/models/current_user_login_response.py +1 -1
  112. vrchatapi/models/current_user_presence.py +1 -1
  113. vrchatapi/models/decline_group_invite_request.py +1 -1
  114. vrchatapi/models/developer_type.py +1 -1
  115. vrchatapi/models/disable2_fa_result.py +1 -1
  116. vrchatapi/models/discord_details.py +1 -1
  117. vrchatapi/models/dynamic_content_row.py +1 -1
  118. vrchatapi/models/earnings_metrics.py +1 -1
  119. vrchatapi/models/earnings_metrics_totals.py +1 -1
  120. vrchatapi/models/economy_account.py +1 -1
  121. vrchatapi/models/economy_account_limits.py +1 -1
  122. vrchatapi/models/economy_balances.py +1 -1
  123. vrchatapi/models/economy_payout.py +1 -1
  124. vrchatapi/models/economy_payout_eligibility.py +1 -1
  125. vrchatapi/models/economy_payout_list.py +1 -1
  126. vrchatapi/models/economy_payout_status.py +1 -1
  127. vrchatapi/models/economy_status.py +1 -1
  128. vrchatapi/models/equip_inventory_item_request.py +1 -1
  129. vrchatapi/models/error.py +1 -1
  130. vrchatapi/models/favorite.py +1 -1
  131. vrchatapi/models/favorite_group.py +1 -1
  132. vrchatapi/models/favorite_group_contents.py +1 -1
  133. vrchatapi/models/favorite_group_contents_entry.py +1 -1
  134. vrchatapi/models/favorite_group_contents_entry_world.py +1 -1
  135. vrchatapi/models/favorite_group_limits.py +1 -1
  136. vrchatapi/models/favorite_group_list.py +1 -1
  137. vrchatapi/models/favorite_group_summary.py +1 -1
  138. vrchatapi/models/favorite_group_visibility.py +1 -1
  139. vrchatapi/models/favorite_limits.py +1 -1
  140. vrchatapi/models/favorite_type.py +1 -1
  141. vrchatapi/models/favorited_world.py +1 -1
  142. vrchatapi/models/feedback.py +1 -1
  143. vrchatapi/models/file.py +1 -1
  144. vrchatapi/models/file_analysis.py +1 -1
  145. vrchatapi/models/file_analysis_avatar_stats.py +1 -1
  146. vrchatapi/models/file_data.py +1 -1
  147. vrchatapi/models/file_status.py +1 -1
  148. vrchatapi/models/file_upload_url.py +1 -1
  149. vrchatapi/models/file_version.py +1 -1
  150. vrchatapi/models/file_version_upload_status.py +1 -1
  151. vrchatapi/models/finish_file_data_upload_request.py +1 -1
  152. vrchatapi/models/follow_calendar_event_request.py +1 -1
  153. vrchatapi/models/friend_status.py +1 -1
  154. vrchatapi/models/group.py +1 -1
  155. vrchatapi/models/group_access_type.py +1 -1
  156. vrchatapi/models/group_announcement.py +1 -1
  157. vrchatapi/models/group_audit_log_entry.py +4 -4
  158. vrchatapi/models/group_audit_log_entry_base.py +1 -1
  159. vrchatapi/models/group_audit_log_entry_boolean_change.py +1 -1
  160. vrchatapi/models/{group_audit_log_entry_event_data.py → group_audit_log_entry_data.py} +412 -334
  161. vrchatapi/models/group_audit_log_entry_data_group_announcement.py +1 -1
  162. vrchatapi/models/group_audit_log_entry_data_group_calendar_event_create.py +1 -1
  163. vrchatapi/models/group_audit_log_entry_data_group_calendar_event_delete.py +1 -1
  164. vrchatapi/models/group_audit_log_entry_data_group_gallery_create.py +1 -1
  165. vrchatapi/models/group_audit_log_entry_data_group_gallery_delete.py +1 -1
  166. vrchatapi/models/group_audit_log_entry_data_group_gallery_update.py +1 -1
  167. vrchatapi/models/group_audit_log_entry_data_group_instance_announcement.py +1 -1
  168. vrchatapi/models/group_audit_log_entry_data_group_instance_close.py +1 -1
  169. vrchatapi/models/group_audit_log_entry_data_group_instance_create.py +1 -1
  170. vrchatapi/models/group_audit_log_entry_data_group_instance_moderation.py +1 -1
  171. vrchatapi/models/group_audit_log_entry_data_group_member_role.py +1 -1
  172. vrchatapi/models/group_audit_log_entry_data_group_member_user_update.py +1 -1
  173. vrchatapi/models/group_audit_log_entry_data_group_post.py +1 -1
  174. vrchatapi/models/group_audit_log_entry_data_group_post_create.py +1 -1
  175. vrchatapi/models/group_audit_log_entry_data_group_post_delete.py +1 -1
  176. vrchatapi/models/group_audit_log_entry_data_group_post_update.py +1 -1
  177. vrchatapi/models/group_audit_log_entry_data_group_role.py +1 -1
  178. vrchatapi/models/group_audit_log_entry_data_group_role_create.py +1 -1
  179. vrchatapi/models/group_audit_log_entry_data_group_role_delete.py +1 -1
  180. vrchatapi/models/group_audit_log_entry_data_group_role_update.py +1 -1
  181. vrchatapi/models/group_audit_log_entry_data_group_update.py +1 -1
  182. vrchatapi/models/group_audit_log_entry_file_id_change.py +1 -1
  183. vrchatapi/models/group_audit_log_entry_group_announcement.py +174 -4
  184. vrchatapi/models/group_audit_log_entry_group_calendar_event_create.py +174 -4
  185. vrchatapi/models/group_audit_log_entry_group_calendar_event_delete.py +174 -4
  186. vrchatapi/models/group_audit_log_entry_group_gallery_create.py +174 -4
  187. vrchatapi/models/group_audit_log_entry_group_gallery_delete.py +174 -4
  188. vrchatapi/models/group_audit_log_entry_group_gallery_update.py +174 -4
  189. vrchatapi/models/group_audit_log_entry_group_instance_announcement.py +174 -4
  190. vrchatapi/models/group_audit_log_entry_group_instance_close.py +174 -4
  191. vrchatapi/models/group_audit_log_entry_group_instance_create.py +174 -4
  192. vrchatapi/models/group_audit_log_entry_group_instance_kick.py +174 -4
  193. vrchatapi/models/group_audit_log_entry_group_instance_warn.py +174 -4
  194. vrchatapi/models/group_audit_log_entry_group_invite_cancel.py +174 -4
  195. vrchatapi/models/group_audit_log_entry_group_invite_create.py +174 -4
  196. vrchatapi/models/group_audit_log_entry_group_member_join.py +174 -4
  197. vrchatapi/models/group_audit_log_entry_group_member_leave.py +174 -4
  198. vrchatapi/models/group_audit_log_entry_group_member_remove.py +174 -4
  199. vrchatapi/models/group_audit_log_entry_group_member_role_assign.py +174 -4
  200. vrchatapi/models/group_audit_log_entry_group_member_role_unassign.py +174 -4
  201. vrchatapi/models/group_audit_log_entry_group_member_user_update.py +174 -4
  202. vrchatapi/models/group_audit_log_entry_group_post_create.py +174 -4
  203. vrchatapi/models/group_audit_log_entry_group_post_delete.py +174 -4
  204. vrchatapi/models/group_audit_log_entry_group_post_update.py +174 -4
  205. vrchatapi/models/group_audit_log_entry_group_request_block.py +174 -4
  206. vrchatapi/models/group_audit_log_entry_group_request_create.py +174 -4
  207. vrchatapi/models/group_audit_log_entry_group_request_reject.py +174 -4
  208. vrchatapi/models/group_audit_log_entry_group_request_withdraw.py +174 -4
  209. vrchatapi/models/group_audit_log_entry_group_role_create.py +174 -4
  210. vrchatapi/models/group_audit_log_entry_group_role_delete.py +174 -4
  211. vrchatapi/models/group_audit_log_entry_group_role_update.py +174 -4
  212. vrchatapi/models/group_audit_log_entry_group_update.py +174 -4
  213. vrchatapi/models/group_audit_log_entry_group_user_ban.py +174 -4
  214. vrchatapi/models/group_audit_log_entry_group_user_unban.py +174 -4
  215. vrchatapi/models/group_audit_log_entry_integer_change.py +1 -1
  216. vrchatapi/models/group_audit_log_entry_join_state_change.py +1 -1
  217. vrchatapi/models/group_audit_log_entry_string_change.py +1 -1
  218. vrchatapi/models/group_audit_log_entry_string_list_change.py +1 -1
  219. vrchatapi/models/group_audit_log_entry_unknown.py +174 -4
  220. vrchatapi/models/group_audit_log_entry_user_id_change.py +1 -1
  221. vrchatapi/models/group_gallery.py +1 -1
  222. vrchatapi/models/group_gallery_file_order.py +1 -1
  223. vrchatapi/models/group_gallery_file_order_request.py +1 -1
  224. vrchatapi/models/group_gallery_image.py +1 -1
  225. vrchatapi/models/group_gallery_image_list.py +1 -1
  226. vrchatapi/models/group_instance.py +1 -1
  227. vrchatapi/models/group_join_request_action.py +1 -1
  228. vrchatapi/models/group_join_state.py +1 -1
  229. vrchatapi/models/group_member.py +1 -1
  230. vrchatapi/models/group_member_limited_user.py +1 -1
  231. vrchatapi/models/group_member_search_response.py +1 -1
  232. vrchatapi/models/group_member_status.py +1 -1
  233. vrchatapi/models/group_my_member.py +1 -1
  234. vrchatapi/models/group_permission.py +1 -1
  235. vrchatapi/models/group_permissions.py +1 -1
  236. vrchatapi/models/group_post.py +1 -1
  237. vrchatapi/models/group_post_visibility.py +1 -1
  238. vrchatapi/models/group_posts_response.py +1 -1
  239. vrchatapi/models/group_privacy.py +1 -1
  240. vrchatapi/models/group_role.py +1 -1
  241. vrchatapi/models/group_role_template.py +1 -1
  242. vrchatapi/models/group_role_template_role.py +1 -1
  243. vrchatapi/models/group_role_template_values.py +1 -1
  244. vrchatapi/models/group_search_sort.py +1 -1
  245. vrchatapi/models/group_transferable.py +1 -1
  246. vrchatapi/models/group_transferable_requirements.py +1 -1
  247. vrchatapi/models/group_user_visibility.py +1 -1
  248. vrchatapi/models/image_animation_style.py +1 -1
  249. vrchatapi/models/image_loop_style.py +1 -1
  250. vrchatapi/models/image_mask.py +1 -1
  251. vrchatapi/models/info_push.py +1 -1
  252. vrchatapi/models/info_push_data.py +1 -1
  253. vrchatapi/models/info_push_data_article.py +1 -1
  254. vrchatapi/models/info_push_data_article_content.py +1 -1
  255. vrchatapi/models/info_push_data_call_to_action.py +1 -1
  256. vrchatapi/models/info_push_data_category.py +1 -1
  257. vrchatapi/models/info_push_data_clickable.py +1 -1
  258. vrchatapi/models/info_push_data_content_source.py +1 -1
  259. vrchatapi/models/info_push_data_content_source_pagination.py +1 -1
  260. vrchatapi/models/info_push_data_control.py +1 -1
  261. vrchatapi/models/info_push_data_control_option.py +1 -1
  262. vrchatapi/models/info_push_data_delivery_behavior.py +1 -1
  263. vrchatapi/models/info_push_data_domain_list_inner.py +1 -1
  264. vrchatapi/models/info_push_data_presentation.py +1 -1
  265. vrchatapi/models/info_push_data_promotion.py +1 -1
  266. vrchatapi/models/info_push_data_promotion_notification.py +1 -1
  267. vrchatapi/models/info_push_data_search.py +1 -1
  268. vrchatapi/models/info_push_embedded_link.py +1 -1
  269. vrchatapi/models/info_push_experiment.py +1 -1
  270. vrchatapi/models/info_push_ips_query.py +1 -1
  271. vrchatapi/models/instance.py +1 -1
  272. vrchatapi/models/instance_category.py +1 -1
  273. vrchatapi/models/instance_content_settings.py +1 -1
  274. vrchatapi/models/instance_platforms.py +1 -1
  275. vrchatapi/models/instance_region.py +1 -1
  276. vrchatapi/models/instance_short_name_response.py +1 -1
  277. vrchatapi/models/instance_type.py +1 -1
  278. vrchatapi/models/instance_vibe.py +1 -1
  279. vrchatapi/models/interests_and_preferences.py +1 -1
  280. vrchatapi/models/inventory.py +1 -1
  281. vrchatapi/models/inventory_asset.py +1 -1
  282. vrchatapi/models/inventory_consumption_results.py +1 -1
  283. vrchatapi/models/inventory_default_attributes1.py +1 -1
  284. vrchatapi/models/inventory_default_attributes1_validator.py +1 -1
  285. vrchatapi/models/inventory_drop.py +1 -1
  286. vrchatapi/models/inventory_equip_slot.py +1 -1
  287. vrchatapi/models/inventory_flag.py +1 -1
  288. vrchatapi/models/inventory_item.py +1 -1
  289. vrchatapi/models/inventory_item_type.py +1 -1
  290. vrchatapi/models/inventory_metadata.py +1 -1
  291. vrchatapi/models/inventory_notification_details.py +1 -1
  292. vrchatapi/models/inventory_spawn.py +1 -1
  293. vrchatapi/models/inventory_template.py +1 -1
  294. vrchatapi/models/inventory_user_attributes.py +1 -1
  295. vrchatapi/models/invite_message.py +1 -1
  296. vrchatapi/models/invite_message_type.py +1 -1
  297. vrchatapi/models/invite_request.py +1 -1
  298. vrchatapi/models/invite_response.py +1 -1
  299. vrchatapi/models/jam.py +1 -1
  300. vrchatapi/models/jam_state_change_dates.py +1 -1
  301. vrchatapi/models/jam_submission.py +1 -1
  302. vrchatapi/models/join_group_request.py +1 -1
  303. vrchatapi/models/license.py +1 -1
  304. vrchatapi/models/license_action.py +1 -1
  305. vrchatapi/models/license_group.py +1 -1
  306. vrchatapi/models/license_type.py +1 -1
  307. vrchatapi/models/limited_group.py +1 -1
  308. vrchatapi/models/limited_unity_package.py +1 -1
  309. vrchatapi/models/limited_user_friend.py +1 -1
  310. vrchatapi/models/limited_user_groups.py +1 -1
  311. vrchatapi/models/limited_user_instance.py +1 -1
  312. vrchatapi/models/limited_user_search.py +1 -1
  313. vrchatapi/models/limited_world.py +1 -1
  314. vrchatapi/models/localized_string.py +1 -1
  315. vrchatapi/models/mime_type.py +1 -1
  316. vrchatapi/models/model_print.py +1 -1
  317. vrchatapi/models/moderate_user_request.py +1 -1
  318. vrchatapi/models/moderation_report.py +1 -1
  319. vrchatapi/models/mutual_friend.py +1 -1
  320. vrchatapi/models/mutuals.py +1 -1
  321. vrchatapi/models/notification.py +1 -1
  322. vrchatapi/models/notification_detail_boop.py +1 -1
  323. vrchatapi/models/notification_detail_invite.py +1 -1
  324. vrchatapi/models/notification_detail_invite_response.py +1 -1
  325. vrchatapi/models/notification_detail_request_invite.py +1 -1
  326. vrchatapi/models/notification_detail_request_invite_response.py +1 -1
  327. vrchatapi/models/notification_detail_vote_to_kick.py +1 -1
  328. vrchatapi/models/notification_type.py +1 -1
  329. vrchatapi/models/notification_v2.py +1 -1
  330. vrchatapi/models/notification_v2_data.py +1 -1
  331. vrchatapi/models/notification_v2_data_badge_earned.py +1 -1
  332. vrchatapi/models/notification_v2_data_boop.py +1 -1
  333. vrchatapi/models/notification_v2_data_event_announcement.py +1 -1
  334. vrchatapi/models/notification_v2_data_group_announcement.py +1 -1
  335. vrchatapi/models/notification_v2_data_group_informative.py +1 -1
  336. vrchatapi/models/notification_v2_data_group_transfer.py +1 -1
  337. vrchatapi/models/notification_v2_details_boop.py +1 -1
  338. vrchatapi/models/notification_v2_response.py +1 -1
  339. vrchatapi/models/notification_v2_type.py +1 -1
  340. vrchatapi/models/o_auth_redirect_code.py +1 -1
  341. vrchatapi/models/ok_status.py +1 -1
  342. vrchatapi/models/ok_status2.py +1 -1
  343. vrchatapi/models/order_option.py +1 -1
  344. vrchatapi/models/order_option_short.py +1 -1
  345. vrchatapi/models/paginated_calendar_event_list.py +1 -1
  346. vrchatapi/models/paginated_group_audit_log_entry_list.py +1 -1
  347. vrchatapi/models/paginated_moderation_report_list.py +1 -1
  348. vrchatapi/models/past_display_name.py +1 -1
  349. vrchatapi/models/pending2_fa_result.py +1 -1
  350. vrchatapi/models/performance_limiter_info.py +1 -1
  351. vrchatapi/models/performance_ratings.py +1 -1
  352. vrchatapi/models/permission.py +1 -1
  353. vrchatapi/models/permission_data.py +1 -1
  354. vrchatapi/models/platform_build_info.py +1 -1
  355. vrchatapi/models/platform_history_entry.py +1 -1
  356. vrchatapi/models/player_moderation.py +1 -1
  357. vrchatapi/models/player_moderation_type.py +1 -1
  358. vrchatapi/models/print_files.py +1 -1
  359. vrchatapi/models/private_profile.py +1 -1
  360. vrchatapi/models/private_profile_activity.py +1 -1
  361. vrchatapi/models/product.py +1 -1
  362. vrchatapi/models/product_listing.py +1 -1
  363. vrchatapi/models/product_listing_attribution.py +1 -1
  364. vrchatapi/models/product_listing_attribution_creator.py +1 -1
  365. vrchatapi/models/product_listing_type.py +1 -1
  366. vrchatapi/models/product_listing_variant.py +1 -1
  367. vrchatapi/models/product_purchase.py +1 -1
  368. vrchatapi/models/product_purchase_history.py +1 -1
  369. vrchatapi/models/product_purchase_location_type.py +1 -1
  370. vrchatapi/models/product_purchase_product.py +1 -1
  371. vrchatapi/models/product_purchase_purchase_context.py +1 -1
  372. vrchatapi/models/product_purchase_record.py +1 -1
  373. vrchatapi/models/product_type.py +1 -1
  374. vrchatapi/models/profile_group.py +1 -1
  375. vrchatapi/models/profile_groups.py +1 -1
  376. vrchatapi/models/profile_represented_group.py +1 -1
  377. vrchatapi/models/prop.py +1 -1
  378. vrchatapi/models/prop_publish_status.py +1 -1
  379. vrchatapi/models/prop_unity_package.py +1 -1
  380. vrchatapi/models/public_profile.py +1 -1
  381. vrchatapi/models/purchase_context_data.py +1 -1
  382. vrchatapi/models/purchase_product_listing_request.py +1 -1
  383. vrchatapi/models/region.py +1 -1
  384. vrchatapi/models/register_user_account_request.py +1 -1
  385. vrchatapi/models/release_status.py +1 -1
  386. vrchatapi/models/report_category.py +1 -1
  387. vrchatapi/models/report_reason.py +1 -1
  388. vrchatapi/models/represented_group.py +1 -1
  389. vrchatapi/models/request_invite_request.py +1 -1
  390. vrchatapi/models/requires_two_factor_auth.py +1 -1
  391. vrchatapi/models/respond_group_join_request.py +1 -1
  392. vrchatapi/models/respond_notification_v2_request.py +1 -1
  393. vrchatapi/models/response.py +1 -1
  394. vrchatapi/models/reward_badge.py +1 -1
  395. vrchatapi/models/reward_redemption.py +1 -1
  396. vrchatapi/models/reward_redemption_data.py +1 -1
  397. vrchatapi/models/reward_redemption_request.py +1 -1
  398. vrchatapi/models/reward_redemption_result.py +1 -1
  399. vrchatapi/models/route_not_implemented.py +1 -1
  400. vrchatapi/models/seller_eligibility.py +1 -1
  401. vrchatapi/models/sent_notification.py +1 -1
  402. vrchatapi/models/sent_notification_details.py +1 -1
  403. vrchatapi/models/service_queue_stats.py +1 -1
  404. vrchatapi/models/service_status.py +1 -1
  405. vrchatapi/models/share_inventory_item_direct_request.py +1 -1
  406. vrchatapi/models/sort_option.py +1 -1
  407. vrchatapi/models/sort_option_product_purchase.py +1 -1
  408. vrchatapi/models/sso_provider.py +1 -1
  409. vrchatapi/models/sso_token.py +1 -1
  410. vrchatapi/models/store.py +1 -1
  411. vrchatapi/models/store_context.py +1 -1
  412. vrchatapi/models/store_shelf.py +1 -1
  413. vrchatapi/models/store_type.py +1 -1
  414. vrchatapi/models/store_view.py +1 -1
  415. vrchatapi/models/submit_moderation_report_request.py +1 -1
  416. vrchatapi/models/submit_moderation_report_request_details.py +1 -1
  417. vrchatapi/models/subscription.py +1 -1
  418. vrchatapi/models/subscription_period.py +1 -1
  419. vrchatapi/models/success.py +1 -1
  420. vrchatapi/models/success_flag.py +1 -1
  421. vrchatapi/models/tilia_kyc.py +1 -1
  422. vrchatapi/models/tilia_status.py +1 -1
  423. vrchatapi/models/tilia_tos.py +1 -1
  424. vrchatapi/models/token_bundle.py +1 -1
  425. vrchatapi/models/transaction.py +1 -1
  426. vrchatapi/models/transaction_agreement.py +1 -1
  427. vrchatapi/models/transaction_status.py +1 -1
  428. vrchatapi/models/transaction_steam_info.py +1 -1
  429. vrchatapi/models/transaction_steam_wallet_info.py +1 -1
  430. vrchatapi/models/transfer_group_request.py +1 -1
  431. vrchatapi/models/tutorial_status.py +1 -1
  432. vrchatapi/models/two_factor_auth_code.py +1 -1
  433. vrchatapi/models/two_factor_auth_type.py +1 -1
  434. vrchatapi/models/two_factor_email_code.py +1 -1
  435. vrchatapi/models/two_factor_recovery_codes.py +1 -1
  436. vrchatapi/models/two_factor_recovery_codes_otp_inner.py +1 -1
  437. vrchatapi/models/unavailable_world.py +1 -1
  438. vrchatapi/models/unity_package.py +1 -1
  439. vrchatapi/models/update_asset_review_notes_request.py +1 -1
  440. vrchatapi/models/update_avatar_request.py +1 -1
  441. vrchatapi/models/update_calendar_event_request.py +1 -1
  442. vrchatapi/models/update_favorite_group_request.py +1 -1
  443. vrchatapi/models/update_group_gallery_request.py +1 -1
  444. vrchatapi/models/update_group_member_request.py +1 -1
  445. vrchatapi/models/update_group_representation_request.py +1 -1
  446. vrchatapi/models/update_group_request.py +1 -1
  447. vrchatapi/models/update_group_role_request.py +1 -1
  448. vrchatapi/models/update_inventory_item_request.py +1 -1
  449. vrchatapi/models/update_invite_message_request.py +1 -1
  450. vrchatapi/models/update_listing_request.py +1 -1
  451. vrchatapi/models/update_product_request.py +1 -1
  452. vrchatapi/models/update_profile_request.py +1 -1
  453. vrchatapi/models/update_prop_request.py +1 -1
  454. vrchatapi/models/update_tilia_tos_request.py +1 -1
  455. vrchatapi/models/update_user_badge_request.py +1 -1
  456. vrchatapi/models/update_user_client_config_request.py +1 -1
  457. vrchatapi/models/update_user_note_request.py +1 -1
  458. vrchatapi/models/update_user_request.py +1 -1
  459. vrchatapi/models/update_world_request.py +1 -1
  460. vrchatapi/models/user.py +1 -1
  461. vrchatapi/models/user_client_config.py +1 -1
  462. vrchatapi/models/user_cosmetic.py +1 -1
  463. vrchatapi/models/user_credits_eligible.py +1 -1
  464. vrchatapi/models/user_exists.py +1 -1
  465. vrchatapi/models/user_group_instance_list_response.py +1 -1
  466. vrchatapi/models/user_note.py +1 -1
  467. vrchatapi/models/user_note_target_user.py +1 -1
  468. vrchatapi/models/user_response.py +1 -1
  469. vrchatapi/models/user_state.py +1 -1
  470. vrchatapi/models/user_status.py +1 -1
  471. vrchatapi/models/user_subscription.py +1 -1
  472. vrchatapi/models/user_subscription_eligible.py +1 -1
  473. vrchatapi/models/verify2_fa_email_code_result.py +1 -1
  474. vrchatapi/models/verify2_fa_result.py +1 -1
  475. vrchatapi/models/verify_auth_token_result.py +1 -1
  476. vrchatapi/models/world.py +1 -1
  477. vrchatapi/models/world_favorite_list.py +1 -1
  478. vrchatapi/models/world_metadata.py +1 -1
  479. vrchatapi/models/world_publish_status.py +1 -1
  480. vrchatapi/rest.py +1 -1
  481. {vrchatapi-1.21.1.dev84.dist-info → vrchatapi-1.22.1.dev1.dist-info}/METADATA +1 -1
  482. vrchatapi-1.22.1.dev1.dist-info/RECORD +486 -0
  483. vrchatapi/models/group_audit_log_entry_event.py +0 -186
  484. vrchatapi-1.21.1.dev84.dist-info/RECORD +0 -487
  485. {vrchatapi-1.21.1.dev84.dist-info → vrchatapi-1.22.1.dev1.dist-info}/WHEEL +0 -0
  486. {vrchatapi-1.21.1.dev84.dist-info → vrchatapi-1.22.1.dev1.dist-info}/licenses/LICENSE +0 -0
  487. {vrchatapi-1.21.1.dev84.dist-info → vrchatapi-1.22.1.dev1.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.21.1-nightly.84
10
+ The version of the OpenAPI document: 1.22.1-nightly.1
11
11
  Generated by: https://openapi-generator.tech
12
12
  """
13
13
 
@@ -182,6 +182,7 @@ from vrchatapi.models.group_announcement import GroupAnnouncement
182
182
  from vrchatapi.models.group_audit_log_entry import GroupAuditLogEntry
183
183
  from vrchatapi.models.group_audit_log_entry_base import GroupAuditLogEntryBase
184
184
  from vrchatapi.models.group_audit_log_entry_boolean_change import GroupAuditLogEntryBooleanChange
185
+ from vrchatapi.models.group_audit_log_entry_data import GroupAuditLogEntryData
185
186
  from vrchatapi.models.group_audit_log_entry_data_group_announcement import GroupAuditLogEntryDataGroupAnnouncement
186
187
  from vrchatapi.models.group_audit_log_entry_data_group_calendar_event_create import GroupAuditLogEntryDataGroupCalendarEventCreate
187
188
  from vrchatapi.models.group_audit_log_entry_data_group_calendar_event_delete import GroupAuditLogEntryDataGroupCalendarEventDelete
@@ -203,8 +204,6 @@ from vrchatapi.models.group_audit_log_entry_data_group_role_create import GroupA
203
204
  from vrchatapi.models.group_audit_log_entry_data_group_role_delete import GroupAuditLogEntryDataGroupRoleDelete
204
205
  from vrchatapi.models.group_audit_log_entry_data_group_role_update import GroupAuditLogEntryDataGroupRoleUpdate
205
206
  from vrchatapi.models.group_audit_log_entry_data_group_update import GroupAuditLogEntryDataGroupUpdate
206
- from vrchatapi.models.group_audit_log_entry_event import GroupAuditLogEntryEvent
207
- from vrchatapi.models.group_audit_log_entry_event_data import GroupAuditLogEntryEventData
208
207
  from vrchatapi.models.group_audit_log_entry_file_id_change import GroupAuditLogEntryFileIDChange
209
208
  from vrchatapi.models.group_audit_log_entry_group_announcement import GroupAuditLogEntryGroupAnnouncement
210
209
  from vrchatapi.models.group_audit_log_entry_group_calendar_event_create import GroupAuditLogEntryGroupCalendarEventCreate
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11
 
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
7
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84\n"\
450
+ "Version of the API: 1.22.1-nightly.1\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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
9
+ The version of the OpenAPI document: 1.22.1-nightly.1
10
10
  Generated by: https://openapi-generator.tech
11
11
  """
12
12
 
@@ -149,6 +149,7 @@ from vrchatapi.models.group_announcement import GroupAnnouncement
149
149
  from vrchatapi.models.group_audit_log_entry import GroupAuditLogEntry
150
150
  from vrchatapi.models.group_audit_log_entry_base import GroupAuditLogEntryBase
151
151
  from vrchatapi.models.group_audit_log_entry_boolean_change import GroupAuditLogEntryBooleanChange
152
+ from vrchatapi.models.group_audit_log_entry_data import GroupAuditLogEntryData
152
153
  from vrchatapi.models.group_audit_log_entry_data_group_announcement import GroupAuditLogEntryDataGroupAnnouncement
153
154
  from vrchatapi.models.group_audit_log_entry_data_group_calendar_event_create import GroupAuditLogEntryDataGroupCalendarEventCreate
154
155
  from vrchatapi.models.group_audit_log_entry_data_group_calendar_event_delete import GroupAuditLogEntryDataGroupCalendarEventDelete
@@ -170,8 +171,6 @@ from vrchatapi.models.group_audit_log_entry_data_group_role_create import GroupA
170
171
  from vrchatapi.models.group_audit_log_entry_data_group_role_delete import GroupAuditLogEntryDataGroupRoleDelete
171
172
  from vrchatapi.models.group_audit_log_entry_data_group_role_update import GroupAuditLogEntryDataGroupRoleUpdate
172
173
  from vrchatapi.models.group_audit_log_entry_data_group_update import GroupAuditLogEntryDataGroupUpdate
173
- from vrchatapi.models.group_audit_log_entry_event import GroupAuditLogEntryEvent
174
- from vrchatapi.models.group_audit_log_entry_event_data import GroupAuditLogEntryEventData
175
174
  from vrchatapi.models.group_audit_log_entry_file_id_change import GroupAuditLogEntryFileIDChange
176
175
  from vrchatapi.models.group_audit_log_entry_group_announcement import GroupAuditLogEntryGroupAnnouncement
177
176
  from vrchatapi.models.group_audit_log_entry_group_calendar_event_create import GroupAuditLogEntryGroupCalendarEventCreate
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
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.21.1-nightly.84
8
+ The version of the OpenAPI document: 1.22.1-nightly.1
9
9
  Generated by: https://openapi-generator.tech
10
10
  """
11
11