vrchatapi 1.22.2.dev6__py3-none-any.whl → 1.22.2.dev7__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.
- vrchatapi/__init__.py +2 -1
- vrchatapi/api/authentication_api.py +1 -1
- vrchatapi/api/avatars_api.py +1 -1
- vrchatapi/api/calendar_api.py +1 -1
- vrchatapi/api/economy_api.py +1 -1
- vrchatapi/api/favorites_api.py +1 -1
- vrchatapi/api/files_api.py +1 -1
- vrchatapi/api/friends_api.py +1 -1
- vrchatapi/api/groups_api.py +1 -1
- vrchatapi/api/instances_api.py +1 -1
- vrchatapi/api/inventory_api.py +1 -1
- vrchatapi/api/invite_api.py +1 -1
- vrchatapi/api/jams_api.py +1 -1
- vrchatapi/api/miscellaneous_api.py +1 -1
- vrchatapi/api/notifications_api.py +1 -1
- vrchatapi/api/playermoderation_api.py +1 -1
- vrchatapi/api/prints_api.py +1 -1
- vrchatapi/api/props_api.py +1 -1
- vrchatapi/api/users_api.py +1 -1
- vrchatapi/api/worlds_api.py +1 -1
- vrchatapi/api_client.py +1 -1
- vrchatapi/configuration.py +2 -2
- vrchatapi/exceptions.py +1 -1
- vrchatapi/models/__init__.py +2 -1
- vrchatapi/models/account_deletion_log.py +1 -1
- vrchatapi/models/add_favorite_request.py +1 -1
- vrchatapi/models/add_group_gallery_image_request.py +1 -1
- vrchatapi/models/admin_asset_bundle.py +1 -1
- vrchatapi/models/admin_unity_package.py +1 -1
- vrchatapi/models/age_verification_status.py +1 -1
- vrchatapi/models/age_verification_status_result.py +1 -1
- vrchatapi/models/agreement.py +1 -1
- vrchatapi/models/agreement_code.py +1 -1
- vrchatapi/models/agreement_request.py +1 -1
- vrchatapi/models/agreement_status.py +1 -1
- vrchatapi/models/api_config.py +1 -1
- vrchatapi/models/api_config_access_logs_urls.py +1 -1
- vrchatapi/models/api_config_announcement.py +1 -1
- vrchatapi/models/api_config_audio_config.py +1 -1
- vrchatapi/models/api_config_avatar_perf_limiter.py +1 -1
- vrchatapi/models/api_config_constants.py +1 -1
- vrchatapi/models/api_config_constants_groups.py +1 -1
- vrchatapi/models/api_config_constants_instance.py +1 -1
- vrchatapi/models/api_config_constants_instancepopulationbrackets.py +1 -1
- vrchatapi/models/api_config_constants_instancepopulationbracketscrowded.py +1 -1
- vrchatapi/models/api_config_constants_instancepopulationbracketsfew.py +1 -1
- vrchatapi/models/api_config_constants_instancepopulationbracketsmany.py +1 -1
- vrchatapi/models/api_config_constants_language.py +1 -1
- vrchatapi/models/api_config_download_url_list.py +1 -1
- vrchatapi/models/api_config_event_shelf_campaign.py +1 -1
- vrchatapi/models/api_config_events.py +1 -1
- vrchatapi/models/api_config_ios_version.py +1 -1
- vrchatapi/models/api_config_loading_screen_weights.py +1 -1
- vrchatapi/models/api_config_low_memory_go_home_timeout_value.py +1 -1
- vrchatapi/models/api_config_min_supported_client_build_number.py +1 -1
- vrchatapi/models/api_config_offline_analysis.py +1 -1
- vrchatapi/models/api_config_profile_defaults.py +1 -1
- vrchatapi/models/api_health.py +1 -1
- vrchatapi/models/avatar.py +1 -1
- vrchatapi/models/avatar_moderation.py +1 -1
- vrchatapi/models/avatar_moderation_created.py +1 -1
- vrchatapi/models/avatar_moderation_type.py +1 -1
- vrchatapi/models/avatar_performance.py +1 -1
- vrchatapi/models/avatar_published_listings_inner.py +1 -1
- vrchatapi/models/avatar_style.py +1 -1
- vrchatapi/models/avatar_styles.py +1 -1
- vrchatapi/models/avatar_unity_package_url_object.py +1 -1
- vrchatapi/models/badge.py +1 -1
- vrchatapi/models/balance.py +1 -1
- vrchatapi/models/ban_group_member_request.py +1 -1
- vrchatapi/models/banner_type.py +112 -0
- vrchatapi/models/bare_error.py +1 -1
- vrchatapi/models/beta.py +1 -1
- vrchatapi/models/beta_registration_not_found_error.py +1 -1
- vrchatapi/models/beta_user_field.py +1 -1
- vrchatapi/models/boop_request.py +1 -1
- vrchatapi/models/calendar_day_of_week.py +1 -1
- vrchatapi/models/calendar_event.py +1 -1
- vrchatapi/models/calendar_event_access.py +1 -1
- vrchatapi/models/calendar_event_category.py +1 -1
- vrchatapi/models/calendar_event_discovery.py +1 -1
- vrchatapi/models/calendar_event_discovery_inclusion.py +1 -1
- vrchatapi/models/calendar_event_discovery_scope.py +1 -1
- vrchatapi/models/calendar_event_frequency.py +1 -1
- vrchatapi/models/calendar_event_occurrence_kind.py +1 -1
- vrchatapi/models/calendar_event_platform.py +1 -1
- vrchatapi/models/calendar_event_recurrence.py +1 -1
- vrchatapi/models/calendar_event_recurrence_end.py +1 -1
- vrchatapi/models/calendar_event_recurrence_end_type.py +1 -1
- vrchatapi/models/calendar_event_user_interest.py +1 -1
- vrchatapi/models/change_user_tags_request.py +1 -1
- vrchatapi/models/change_world_tags_request.py +1 -1
- vrchatapi/models/content_filter.py +1 -1
- vrchatapi/models/create_avatar_moderation_request.py +1 -1
- vrchatapi/models/create_avatar_request.py +1 -1
- vrchatapi/models/create_avatar_request_release_status.py +1 -1
- vrchatapi/models/create_calendar_event_request.py +1 -1
- vrchatapi/models/create_file_request.py +1 -1
- vrchatapi/models/create_file_request_mime_type.py +1 -1
- vrchatapi/models/create_file_version_request.py +1 -1
- vrchatapi/models/create_group_announcement_request.py +1 -1
- vrchatapi/models/create_group_gallery_request.py +1 -1
- vrchatapi/models/create_group_invite_request.py +1 -1
- vrchatapi/models/create_group_post_request.py +1 -1
- vrchatapi/models/create_group_request.py +1 -1
- vrchatapi/models/create_group_role_request.py +1 -1
- vrchatapi/models/create_instance_request.py +1 -1
- vrchatapi/models/create_instance_request_region.py +1 -1
- vrchatapi/models/create_jam_submission_request.py +1 -1
- vrchatapi/models/create_listing_request.py +1 -1
- vrchatapi/models/create_product_request.py +1 -1
- vrchatapi/models/create_product_request_type.py +1 -1
- vrchatapi/models/create_prop_request.py +1 -1
- vrchatapi/models/create_world_request.py +1 -1
- vrchatapi/models/create_world_request_release_status.py +1 -1
- vrchatapi/models/current_user.py +4 -4
- vrchatapi/models/current_user_login_response.py +4 -4
- vrchatapi/models/current_user_presence.py +4 -4
- vrchatapi/models/decline_group_invite_request.py +1 -1
- vrchatapi/models/developer_type.py +1 -1
- vrchatapi/models/disable2_fa_result.py +1 -1
- vrchatapi/models/discord_details.py +1 -1
- vrchatapi/models/dynamic_content_row.py +1 -1
- vrchatapi/models/earnings_metrics.py +1 -1
- vrchatapi/models/earnings_metrics_totals.py +1 -1
- vrchatapi/models/economy_account.py +1 -1
- vrchatapi/models/economy_account_limits.py +1 -1
- vrchatapi/models/economy_balances.py +1 -1
- vrchatapi/models/economy_payout.py +1 -1
- vrchatapi/models/economy_payout_eligibility.py +1 -1
- vrchatapi/models/economy_payout_list.py +1 -1
- vrchatapi/models/economy_payout_status.py +1 -1
- vrchatapi/models/economy_status.py +1 -1
- vrchatapi/models/equip_inventory_item_request.py +1 -1
- vrchatapi/models/error.py +1 -1
- vrchatapi/models/favorite.py +1 -1
- vrchatapi/models/favorite_group.py +1 -1
- vrchatapi/models/favorite_group_contents.py +1 -1
- vrchatapi/models/favorite_group_contents_entry.py +1 -1
- vrchatapi/models/favorite_group_contents_entry_world.py +1 -1
- vrchatapi/models/favorite_group_limits.py +1 -1
- vrchatapi/models/favorite_group_list.py +1 -1
- vrchatapi/models/favorite_group_summary.py +1 -1
- vrchatapi/models/favorite_group_visibility.py +1 -1
- vrchatapi/models/favorite_limits.py +1 -1
- vrchatapi/models/favorite_type.py +1 -1
- vrchatapi/models/favorited_world.py +1 -1
- vrchatapi/models/feedback.py +1 -1
- vrchatapi/models/file.py +1 -1
- vrchatapi/models/file_analysis.py +1 -1
- vrchatapi/models/file_analysis_avatar_stats.py +1 -1
- vrchatapi/models/file_data.py +1 -1
- vrchatapi/models/file_status.py +1 -1
- vrchatapi/models/file_upload_url.py +1 -1
- vrchatapi/models/file_version.py +1 -1
- vrchatapi/models/file_version_upload_status.py +1 -1
- vrchatapi/models/finish_file_data_upload_request.py +1 -1
- vrchatapi/models/follow_calendar_event_request.py +1 -1
- vrchatapi/models/friend_status.py +1 -1
- vrchatapi/models/group.py +1 -1
- vrchatapi/models/group_access_type.py +1 -1
- vrchatapi/models/group_announcement.py +1 -1
- vrchatapi/models/group_audit_log_entry.py +1 -1
- vrchatapi/models/group_audit_log_entry_base.py +1 -1
- vrchatapi/models/group_audit_log_entry_boolean_change.py +1 -1
- vrchatapi/models/group_audit_log_entry_data.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_announcement.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_calendar_event_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_calendar_event_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_gallery_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_gallery_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_gallery_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_instance_announcement.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_instance_close.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_instance_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_instance_moderation.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_member_role.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_member_user_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_post.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_post_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_post_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_post_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_role.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_role_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_role_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_role_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_data_group_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_file_id_change.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_announcement.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_calendar_event_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_calendar_event_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_gallery_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_gallery_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_gallery_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_instance_announcement.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_instance_close.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_instance_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_instance_kick.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_instance_warn.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_invite_cancel.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_invite_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_member_join.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_member_leave.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_member_remove.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_member_role_assign.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_member_role_unassign.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_member_user_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_post_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_post_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_post_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_request_block.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_request_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_request_reject.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_request_withdraw.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_role_create.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_role_delete.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_role_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_update.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_user_ban.py +1 -1
- vrchatapi/models/group_audit_log_entry_group_user_unban.py +1 -1
- vrchatapi/models/group_audit_log_entry_integer_change.py +1 -1
- vrchatapi/models/group_audit_log_entry_join_state_change.py +1 -1
- vrchatapi/models/group_audit_log_entry_string_change.py +1 -1
- vrchatapi/models/group_audit_log_entry_string_list_change.py +1 -1
- vrchatapi/models/group_audit_log_entry_unknown.py +1 -1
- vrchatapi/models/group_audit_log_entry_user_id_change.py +1 -1
- vrchatapi/models/group_gallery.py +1 -1
- vrchatapi/models/group_gallery_file_order.py +1 -1
- vrchatapi/models/group_gallery_file_order_request.py +1 -1
- vrchatapi/models/group_gallery_image.py +1 -1
- vrchatapi/models/group_gallery_image_list.py +1 -1
- vrchatapi/models/group_instance.py +1 -1
- vrchatapi/models/group_join_request_action.py +1 -1
- vrchatapi/models/group_join_state.py +1 -1
- vrchatapi/models/group_member.py +1 -1
- vrchatapi/models/group_member_limited_user.py +4 -4
- vrchatapi/models/group_member_search_response.py +1 -1
- vrchatapi/models/group_member_status.py +1 -1
- vrchatapi/models/group_my_member.py +1 -1
- vrchatapi/models/group_permission.py +1 -1
- vrchatapi/models/group_permissions.py +1 -1
- vrchatapi/models/group_post.py +1 -1
- vrchatapi/models/group_post_visibility.py +1 -1
- vrchatapi/models/group_posts_response.py +1 -1
- vrchatapi/models/group_privacy.py +1 -1
- vrchatapi/models/group_role.py +1 -1
- vrchatapi/models/group_role_template.py +1 -1
- vrchatapi/models/group_role_template_role.py +1 -1
- vrchatapi/models/group_role_template_values.py +1 -1
- vrchatapi/models/group_search_sort.py +1 -1
- vrchatapi/models/group_transferable.py +1 -1
- vrchatapi/models/group_transferable_requirements.py +1 -1
- vrchatapi/models/group_user_visibility.py +1 -1
- vrchatapi/models/image_animation_style.py +1 -1
- vrchatapi/models/image_loop_style.py +1 -1
- vrchatapi/models/image_mask.py +1 -1
- vrchatapi/models/info_push.py +1 -1
- vrchatapi/models/info_push_data.py +1 -1
- vrchatapi/models/info_push_data_article.py +1 -1
- vrchatapi/models/info_push_data_article_content.py +1 -1
- vrchatapi/models/info_push_data_call_to_action.py +1 -1
- vrchatapi/models/info_push_data_category.py +1 -1
- vrchatapi/models/info_push_data_clickable.py +1 -1
- vrchatapi/models/info_push_data_content_source.py +1 -1
- vrchatapi/models/info_push_data_content_source_pagination.py +1 -1
- vrchatapi/models/info_push_data_control.py +1 -1
- vrchatapi/models/info_push_data_control_option.py +1 -1
- vrchatapi/models/info_push_data_delivery_behavior.py +1 -1
- vrchatapi/models/info_push_data_domain_list_inner.py +1 -1
- vrchatapi/models/info_push_data_presentation.py +1 -1
- vrchatapi/models/info_push_data_promotion.py +1 -1
- vrchatapi/models/info_push_data_promotion_notification.py +1 -1
- vrchatapi/models/info_push_data_search.py +1 -1
- vrchatapi/models/info_push_embedded_link.py +1 -1
- vrchatapi/models/info_push_experiment.py +1 -1
- vrchatapi/models/info_push_ips_query.py +1 -1
- vrchatapi/models/instance.py +1 -1
- vrchatapi/models/instance_category.py +1 -1
- vrchatapi/models/instance_content_settings.py +1 -1
- vrchatapi/models/instance_platforms.py +1 -1
- vrchatapi/models/instance_region.py +1 -1
- vrchatapi/models/instance_short_name_response.py +1 -1
- vrchatapi/models/instance_type.py +1 -1
- vrchatapi/models/instance_vibe.py +1 -1
- vrchatapi/models/interests_and_preferences.py +1 -1
- vrchatapi/models/inventory.py +1 -1
- vrchatapi/models/inventory_asset.py +1 -1
- vrchatapi/models/inventory_consumption_results.py +1 -1
- vrchatapi/models/inventory_default_attributes1.py +1 -1
- vrchatapi/models/inventory_default_attributes1_validator.py +1 -1
- vrchatapi/models/inventory_drop.py +1 -1
- vrchatapi/models/inventory_equip_slot.py +1 -1
- vrchatapi/models/inventory_flag.py +1 -1
- vrchatapi/models/inventory_item.py +1 -1
- vrchatapi/models/inventory_item_type.py +1 -1
- vrchatapi/models/inventory_metadata.py +1 -1
- vrchatapi/models/inventory_notification_details.py +1 -1
- vrchatapi/models/inventory_sort_order.py +1 -1
- vrchatapi/models/inventory_spawn.py +1 -1
- vrchatapi/models/inventory_template.py +1 -1
- vrchatapi/models/inventory_user_attributes.py +1 -1
- vrchatapi/models/invite_message.py +1 -1
- vrchatapi/models/invite_message_type.py +1 -1
- vrchatapi/models/invite_request.py +1 -1
- vrchatapi/models/invite_response.py +1 -1
- vrchatapi/models/jam.py +1 -1
- vrchatapi/models/jam_state_change_dates.py +1 -1
- vrchatapi/models/jam_submission.py +1 -1
- vrchatapi/models/join_group_request.py +1 -1
- vrchatapi/models/license.py +1 -1
- vrchatapi/models/license_action.py +1 -1
- vrchatapi/models/license_group.py +1 -1
- vrchatapi/models/license_type.py +1 -1
- vrchatapi/models/limited_group.py +1 -1
- vrchatapi/models/limited_unity_package.py +1 -1
- vrchatapi/models/limited_user_friend.py +4 -4
- vrchatapi/models/limited_user_groups.py +1 -1
- vrchatapi/models/limited_user_instance.py +1 -1
- vrchatapi/models/limited_user_search.py +4 -4
- vrchatapi/models/limited_world.py +1 -1
- vrchatapi/models/localized_string.py +1 -1
- vrchatapi/models/mime_type.py +1 -1
- vrchatapi/models/model_print.py +1 -1
- vrchatapi/models/moderate_user_request.py +1 -1
- vrchatapi/models/moderation_report.py +1 -1
- vrchatapi/models/mutual_friend.py +4 -4
- vrchatapi/models/mutuals.py +1 -1
- vrchatapi/models/notification.py +1 -1
- vrchatapi/models/notification_base.py +1 -1
- vrchatapi/models/notification_boop.py +1 -1
- vrchatapi/models/notification_detail_boop.py +1 -1
- vrchatapi/models/notification_detail_invite.py +1 -1
- vrchatapi/models/notification_detail_invite_response.py +1 -1
- vrchatapi/models/notification_detail_request_invite.py +1 -1
- vrchatapi/models/notification_detail_request_invite_response.py +1 -1
- vrchatapi/models/notification_detail_vote_to_kick.py +1 -1
- vrchatapi/models/notification_friend_request.py +1 -1
- vrchatapi/models/notification_invite.py +1 -1
- vrchatapi/models/notification_invite_response.py +1 -1
- vrchatapi/models/notification_message.py +1 -1
- vrchatapi/models/notification_request_invite.py +1 -1
- vrchatapi/models/notification_request_invite_response.py +1 -1
- vrchatapi/models/notification_type.py +1 -1
- vrchatapi/models/notification_unknown.py +1 -1
- vrchatapi/models/notification_v2.py +1 -1
- vrchatapi/models/notification_v2_data.py +1 -1
- vrchatapi/models/notification_v2_data_badge_earned.py +1 -1
- vrchatapi/models/notification_v2_data_boop.py +1 -1
- vrchatapi/models/notification_v2_data_event_announcement.py +1 -1
- vrchatapi/models/notification_v2_data_group_announcement.py +1 -1
- vrchatapi/models/notification_v2_data_group_informative.py +1 -1
- vrchatapi/models/notification_v2_data_group_transfer.py +1 -1
- vrchatapi/models/notification_v2_details_boop.py +1 -1
- vrchatapi/models/notification_v2_response.py +1 -1
- vrchatapi/models/notification_v2_type.py +1 -1
- vrchatapi/models/notification_vote_to_kick.py +1 -1
- vrchatapi/models/o_auth_redirect_code.py +1 -1
- vrchatapi/models/ok_status.py +1 -1
- vrchatapi/models/ok_status2.py +1 -1
- vrchatapi/models/order_option.py +1 -1
- vrchatapi/models/order_option_short.py +1 -1
- vrchatapi/models/paginated_calendar_event_list.py +1 -1
- vrchatapi/models/paginated_group_audit_log_entry_list.py +1 -1
- vrchatapi/models/paginated_moderation_report_list.py +1 -1
- vrchatapi/models/past_display_name.py +1 -1
- vrchatapi/models/pending2_fa_result.py +1 -1
- vrchatapi/models/performance_limiter_info.py +1 -1
- vrchatapi/models/performance_ratings.py +1 -1
- vrchatapi/models/permission.py +1 -1
- vrchatapi/models/permission_data.py +1 -1
- vrchatapi/models/platform_build_info.py +1 -1
- vrchatapi/models/platform_history_entry.py +1 -1
- vrchatapi/models/player_moderation.py +1 -1
- vrchatapi/models/player_moderation_type.py +1 -1
- vrchatapi/models/print_files.py +1 -1
- vrchatapi/models/private_profile.py +1 -1
- vrchatapi/models/private_profile_activity.py +1 -1
- vrchatapi/models/product.py +1 -1
- vrchatapi/models/product_listing.py +1 -1
- vrchatapi/models/product_listing_attribution.py +1 -1
- vrchatapi/models/product_listing_attribution_creator.py +1 -1
- vrchatapi/models/product_listing_type.py +1 -1
- vrchatapi/models/product_listing_variant.py +1 -1
- vrchatapi/models/product_purchase.py +1 -1
- vrchatapi/models/product_purchase_history.py +1 -1
- vrchatapi/models/product_purchase_location_type.py +1 -1
- vrchatapi/models/product_purchase_product.py +1 -1
- vrchatapi/models/product_purchase_purchase_context.py +1 -1
- vrchatapi/models/product_purchase_record.py +1 -1
- vrchatapi/models/product_type.py +1 -1
- vrchatapi/models/profile_group.py +1 -1
- vrchatapi/models/profile_groups.py +1 -1
- vrchatapi/models/profile_represented_group.py +1 -1
- vrchatapi/models/prop.py +1 -1
- vrchatapi/models/prop_publish_status.py +1 -1
- vrchatapi/models/prop_unity_package.py +1 -1
- vrchatapi/models/public_profile.py +4 -4
- vrchatapi/models/purchase_context_data.py +1 -1
- vrchatapi/models/purchase_product_listing_request.py +1 -1
- vrchatapi/models/region.py +1 -1
- vrchatapi/models/register_user_account_request.py +1 -1
- vrchatapi/models/release_status.py +1 -1
- vrchatapi/models/report_category.py +1 -1
- vrchatapi/models/report_reason.py +1 -1
- vrchatapi/models/represented_group.py +1 -1
- vrchatapi/models/request_invite_request.py +1 -1
- vrchatapi/models/requires_two_factor_auth.py +1 -1
- vrchatapi/models/respond_group_join_request.py +1 -1
- vrchatapi/models/respond_notification_v2_request.py +1 -1
- vrchatapi/models/response.py +1 -1
- vrchatapi/models/reward_badge.py +1 -1
- vrchatapi/models/reward_redemption.py +1 -1
- vrchatapi/models/reward_redemption_data.py +1 -1
- vrchatapi/models/reward_redemption_request.py +1 -1
- vrchatapi/models/reward_redemption_result.py +1 -1
- vrchatapi/models/route_not_implemented.py +1 -1
- vrchatapi/models/seller_eligibility.py +1 -1
- vrchatapi/models/sent_notification.py +1 -1
- vrchatapi/models/sent_notification_details.py +1 -1
- vrchatapi/models/service_queue_stats.py +1 -1
- vrchatapi/models/service_status.py +1 -1
- vrchatapi/models/share_inventory_item_direct_request.py +1 -1
- vrchatapi/models/sort_option.py +1 -1
- vrchatapi/models/sort_option_avatar.py +1 -1
- vrchatapi/models/sort_option_product_purchase.py +1 -1
- vrchatapi/models/sso_provider.py +1 -1
- vrchatapi/models/sso_token.py +1 -1
- vrchatapi/models/store.py +1 -1
- vrchatapi/models/store_context.py +1 -1
- vrchatapi/models/store_shelf.py +1 -1
- vrchatapi/models/store_type.py +1 -1
- vrchatapi/models/store_view.py +1 -1
- vrchatapi/models/submit_moderation_report_request.py +1 -1
- vrchatapi/models/submit_moderation_report_request_details.py +1 -1
- vrchatapi/models/subscription.py +1 -1
- vrchatapi/models/subscription_period.py +1 -1
- vrchatapi/models/success.py +1 -1
- vrchatapi/models/success_flag.py +1 -1
- vrchatapi/models/tilia_kyc.py +1 -1
- vrchatapi/models/tilia_status.py +1 -1
- vrchatapi/models/tilia_tos.py +1 -1
- vrchatapi/models/token_bundle.py +1 -1
- vrchatapi/models/transaction.py +1 -1
- vrchatapi/models/transaction_agreement.py +1 -1
- vrchatapi/models/transaction_status.py +1 -1
- vrchatapi/models/transaction_steam_info.py +1 -1
- vrchatapi/models/transaction_steam_wallet_info.py +1 -1
- vrchatapi/models/transfer_group_request.py +1 -1
- vrchatapi/models/tutorial_status.py +1 -1
- vrchatapi/models/two_factor_auth_code.py +1 -1
- vrchatapi/models/two_factor_auth_type.py +1 -1
- vrchatapi/models/two_factor_email_code.py +1 -1
- vrchatapi/models/two_factor_recovery_codes.py +1 -1
- vrchatapi/models/two_factor_recovery_codes_otp_inner.py +1 -1
- vrchatapi/models/unavailable_world.py +1 -1
- vrchatapi/models/unity_package.py +1 -1
- vrchatapi/models/update_asset_review_notes_request.py +1 -1
- vrchatapi/models/update_avatar_request.py +1 -1
- vrchatapi/models/update_avatar_request_release_status.py +1 -1
- vrchatapi/models/update_calendar_event_request.py +1 -1
- vrchatapi/models/update_favorite_group_request.py +1 -1
- vrchatapi/models/update_group_gallery_request.py +1 -1
- vrchatapi/models/update_group_member_request.py +1 -1
- vrchatapi/models/update_group_representation_request.py +1 -1
- vrchatapi/models/update_group_request.py +1 -1
- vrchatapi/models/update_group_role_request.py +1 -1
- vrchatapi/models/update_instance_request.py +1 -1
- vrchatapi/models/update_inventory_item_request.py +1 -1
- vrchatapi/models/update_invite_message_request.py +1 -1
- vrchatapi/models/update_listing_request.py +1 -1
- vrchatapi/models/update_product_request.py +1 -1
- vrchatapi/models/update_profile_request.py +4 -10
- vrchatapi/models/update_prop_request.py +1 -1
- vrchatapi/models/update_tilia_tos_request.py +1 -1
- vrchatapi/models/update_user_badge_request.py +1 -1
- vrchatapi/models/update_user_client_config_request.py +1 -1
- vrchatapi/models/update_user_note_request.py +1 -1
- vrchatapi/models/update_user_request.py +56 -2
- vrchatapi/models/update_world_request.py +1 -1
- vrchatapi/models/user.py +4 -4
- vrchatapi/models/user_client_config.py +1 -1
- vrchatapi/models/user_cosmetic.py +1 -1
- vrchatapi/models/user_credits_eligible.py +1 -1
- vrchatapi/models/user_exists.py +1 -1
- vrchatapi/models/user_group_instance_list_response.py +1 -1
- vrchatapi/models/user_note.py +1 -1
- vrchatapi/models/user_note_target_user.py +1 -1
- vrchatapi/models/user_response.py +4 -4
- vrchatapi/models/user_search_sort.py +1 -1
- vrchatapi/models/user_state.py +1 -1
- vrchatapi/models/user_status.py +1 -1
- vrchatapi/models/user_subscription.py +1 -1
- vrchatapi/models/user_subscription_eligible.py +1 -1
- vrchatapi/models/verify2_fa_email_code_result.py +1 -1
- vrchatapi/models/verify2_fa_result.py +1 -1
- vrchatapi/models/verify_auth_token_result.py +1 -1
- vrchatapi/models/websocket_clear_notification.py +1 -1
- vrchatapi/models/websocket_content_refresh.py +1 -1
- vrchatapi/models/websocket_content_refresh_action_type.py +1 -1
- vrchatapi/models/websocket_content_refresh_encoded.py +1 -1
- vrchatapi/models/websocket_friend_active.py +1 -1
- vrchatapi/models/websocket_friend_active_encoded.py +1 -1
- vrchatapi/models/websocket_friend_add.py +1 -1
- vrchatapi/models/websocket_friend_add_encoded.py +1 -1
- vrchatapi/models/websocket_friend_delete.py +1 -1
- vrchatapi/models/websocket_friend_delete_encoded.py +1 -1
- vrchatapi/models/websocket_friend_location.py +1 -1
- vrchatapi/models/websocket_friend_location_encoded.py +1 -1
- vrchatapi/models/websocket_friend_offline.py +1 -1
- vrchatapi/models/websocket_friend_offline_encoded.py +1 -1
- vrchatapi/models/websocket_friend_online.py +1 -1
- vrchatapi/models/websocket_friend_online_encoded.py +1 -1
- vrchatapi/models/websocket_friend_update.py +1 -1
- vrchatapi/models/websocket_friend_update_encoded.py +1 -1
- vrchatapi/models/websocket_group_joined.py +1 -1
- vrchatapi/models/websocket_group_joined_encoded.py +1 -1
- vrchatapi/models/websocket_group_left.py +1 -1
- vrchatapi/models/websocket_group_left_encoded.py +1 -1
- vrchatapi/models/websocket_group_member_updated.py +1 -1
- vrchatapi/models/websocket_group_member_updated_encoded.py +1 -1
- vrchatapi/models/websocket_group_role_updated.py +1 -1
- vrchatapi/models/websocket_group_role_updated_encoded.py +1 -1
- vrchatapi/models/websocket_hide_notification.py +1 -1
- vrchatapi/models/websocket_instance_queue_joined.py +1 -1
- vrchatapi/models/websocket_instance_queue_joined_encoded.py +1 -1
- vrchatapi/models/websocket_instance_queue_ready.py +1 -1
- vrchatapi/models/websocket_instance_queue_ready_encoded.py +1 -1
- vrchatapi/models/websocket_message.py +1 -1
- vrchatapi/models/websocket_message_unknown.py +1 -1
- vrchatapi/models/websocket_notification.py +1 -1
- vrchatapi/models/websocket_notification_detail_boop.py +1 -1
- vrchatapi/models/websocket_notification_detail_invite.py +1 -1
- vrchatapi/models/websocket_notification_detail_invite_response.py +1 -1
- vrchatapi/models/websocket_notification_detail_request_invite.py +1 -1
- vrchatapi/models/websocket_notification_detail_request_invite_response.py +1 -1
- vrchatapi/models/websocket_notification_detail_vote_to_kick.py +1 -1
- vrchatapi/models/websocket_notification_encoded.py +1 -1
- vrchatapi/models/websocket_notification_unknown.py +1 -1
- vrchatapi/models/websocket_notification_v2_delete.py +1 -1
- vrchatapi/models/websocket_notification_v2_delete_encoded.py +1 -1
- vrchatapi/models/websocket_notification_v2_encoded.py +1 -1
- vrchatapi/models/websocket_notification_v2_update.py +1 -1
- vrchatapi/models/websocket_notification_v2_update_encoded.py +1 -1
- vrchatapi/models/websocket_response_notification.py +1 -1
- vrchatapi/models/websocket_response_notification_encoded.py +1 -1
- vrchatapi/models/websocket_see_notification.py +1 -1
- vrchatapi/models/websocket_user_badge_assigned.py +1 -1
- vrchatapi/models/websocket_user_badge_assigned_encoded.py +1 -1
- vrchatapi/models/websocket_user_badge_unassigned.py +1 -1
- vrchatapi/models/websocket_user_badge_unassigned_encoded.py +1 -1
- vrchatapi/models/websocket_user_location.py +1 -1
- vrchatapi/models/websocket_user_location_encoded.py +1 -1
- vrchatapi/models/websocket_user_update.py +1 -1
- vrchatapi/models/websocket_user_update_encoded.py +1 -1
- vrchatapi/models/world.py +1 -1
- vrchatapi/models/world_favorite_list.py +1 -1
- vrchatapi/models/world_metadata.py +1 -1
- vrchatapi/models/world_publish_status.py +1 -1
- vrchatapi/rest.py +1 -1
- {vrchatapi-1.22.2.dev6.dist-info → vrchatapi-1.22.2.dev7.dist-info}/METADATA +1 -1
- vrchatapi-1.22.2.dev7.dist-info/RECORD +565 -0
- vrchatapi-1.22.2.dev6.dist-info/RECORD +0 -564
- {vrchatapi-1.22.2.dev6.dist-info → vrchatapi-1.22.2.dev7.dist-info}/WHEEL +0 -0
- {vrchatapi-1.22.2.dev6.dist-info → vrchatapi-1.22.2.dev7.dist-info}/licenses/LICENSE +0 -0
- {vrchatapi-1.22.2.dev6.dist-info → vrchatapi-1.22.2.dev7.dist-info}/top_level.txt +0 -0
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
vrchatapi/models/current_user.py
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -50,7 +50,7 @@ class CurrentUser(object):
|
|
|
50
50
|
'apple_id': 'str',
|
|
51
51
|
'auth_token': 'str',
|
|
52
52
|
'banner_color': 'str',
|
|
53
|
-
'banner_type': '
|
|
53
|
+
'banner_type': 'BannerType',
|
|
54
54
|
'banner_url': 'str',
|
|
55
55
|
'completed_tutorials': 'list[str]',
|
|
56
56
|
'content_filters': 'list[str]',
|
|
@@ -819,7 +819,7 @@ class CurrentUser(object):
|
|
|
819
819
|
|
|
820
820
|
|
|
821
821
|
:return: The banner_type of this CurrentUser. # noqa: E501
|
|
822
|
-
:rtype:
|
|
822
|
+
:rtype: BannerType
|
|
823
823
|
"""
|
|
824
824
|
return self._banner_type
|
|
825
825
|
|
|
@@ -829,7 +829,7 @@ class CurrentUser(object):
|
|
|
829
829
|
|
|
830
830
|
|
|
831
831
|
:param banner_type: The banner_type of this CurrentUser. # noqa: E501
|
|
832
|
-
:type banner_type:
|
|
832
|
+
:type banner_type: BannerType
|
|
833
833
|
"""
|
|
834
834
|
|
|
835
835
|
self._banner_type = banner_type
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -50,7 +50,7 @@ class CurrentUserLoginResponse(object):
|
|
|
50
50
|
'apple_id': 'str',
|
|
51
51
|
'auth_token': 'str',
|
|
52
52
|
'banner_color': 'str',
|
|
53
|
-
'banner_type': '
|
|
53
|
+
'banner_type': 'BannerType',
|
|
54
54
|
'banner_url': 'str',
|
|
55
55
|
'completed_tutorials': 'list[str]',
|
|
56
56
|
'content_filters': 'list[str]',
|
|
@@ -858,7 +858,7 @@ class CurrentUserLoginResponse(object):
|
|
|
858
858
|
|
|
859
859
|
|
|
860
860
|
:return: The banner_type of this CurrentUserLoginResponse. # noqa: E501
|
|
861
|
-
:rtype:
|
|
861
|
+
:rtype: BannerType
|
|
862
862
|
"""
|
|
863
863
|
return self._banner_type
|
|
864
864
|
|
|
@@ -868,7 +868,7 @@ class CurrentUserLoginResponse(object):
|
|
|
868
868
|
|
|
869
869
|
|
|
870
870
|
:param banner_type: The banner_type of this CurrentUserLoginResponse. # noqa: E501
|
|
871
|
-
:type banner_type:
|
|
871
|
+
:type banner_type: BannerType
|
|
872
872
|
"""
|
|
873
873
|
|
|
874
874
|
self._banner_type = banner_type
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -40,7 +40,7 @@ class CurrentUserPresence(object):
|
|
|
40
40
|
'avatar_thumbnail': 'str',
|
|
41
41
|
'banner': 'str',
|
|
42
42
|
'banner_color': 'str',
|
|
43
|
-
'banner_type': '
|
|
43
|
+
'banner_type': 'BannerType',
|
|
44
44
|
'banner_url': 'str',
|
|
45
45
|
'current_avatar_tags': 'str',
|
|
46
46
|
'debugflag': 'str',
|
|
@@ -258,7 +258,7 @@ class CurrentUserPresence(object):
|
|
|
258
258
|
|
|
259
259
|
|
|
260
260
|
:return: The banner_type of this CurrentUserPresence. # noqa: E501
|
|
261
|
-
:rtype:
|
|
261
|
+
:rtype: BannerType
|
|
262
262
|
"""
|
|
263
263
|
return self._banner_type
|
|
264
264
|
|
|
@@ -268,7 +268,7 @@ class CurrentUserPresence(object):
|
|
|
268
268
|
|
|
269
269
|
|
|
270
270
|
:param banner_type: The banner_type of this CurrentUserPresence. # noqa: E501
|
|
271
|
-
:type banner_type:
|
|
271
|
+
:type banner_type: BannerType
|
|
272
272
|
"""
|
|
273
273
|
|
|
274
274
|
self._banner_type = banner_type
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|
vrchatapi/models/error.py
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API. _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._ Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself. Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying. **Something wrong or missing?** The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one: - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about. Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly). # noqa: E501
|
|
7
7
|
|
|
8
|
-
The version of the OpenAPI document: 1.22.2-nightly.
|
|
8
|
+
The version of the OpenAPI document: 1.22.2-nightly.7
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
10
10
|
"""
|
|
11
11
|
|