mudbase 1.1.8 → 1.2.1

data/docs/MultiRoleFeatureApi.md

@@ -1,654 +0,0 @@
-# Mudbase::MultiRoleFeatureApi
-
-All URIs are relative to *https://cloud.mudbase.dev*
-
-| Method | HTTP request | Description |
-| ------ | ------------ | ----------- |
-| [**add_custom_role**](MultiRoleFeatureApi.md#add_custom_role) | **POST** /api/projects/{projectId}/multi-role/roles | Add custom role |
-| [**get_available_roles**](MultiRoleFeatureApi.md#get_available_roles) | **GET** /api/projects/{projectId}/multi-role/roles/available | Get available roles for signup |
-| [**get_multi_role_config**](MultiRoleFeatureApi.md#get_multi_role_config) | **GET** /api/projects/{projectId}/multi-role | Get multi-role feature configuration |
-| [**oauth_signup_with_role**](MultiRoleFeatureApi.md#oauth_signup_with_role) | **GET** /api/auth/oauth/signup/{role}/{provider}/{projectId} | OAuth signup with specific role |
-| [**register_with_role**](MultiRoleFeatureApi.md#register_with_role) | **POST** /api/auth/local/signup/{role} | Register user with specific role (Local Auth) |
-| [**toggle_role**](MultiRoleFeatureApi.md#toggle_role) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug}/toggle | Toggle role on/off |
-| [**update_collection_permissions**](MultiRoleFeatureApi.md#update_collection_permissions) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug}/collections/{collectionId}/permissions | Update collection permissions for a role |
-| [**update_multi_role_settings**](MultiRoleFeatureApi.md#update_multi_role_settings) | **PATCH** /api/projects/{projectId}/multi-role/settings | Update multi-role feature settings |
-| [**update_project_role**](MultiRoleFeatureApi.md#update_project_role) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug} | Update role configuration |
-
-
-## add_custom_role
-
-> <UpdateMultiRoleSettings200Response> add_custom_role(project_id, add_custom_role_request)
-
-Add custom role
-
-Add a custom role to a project with specific permissions and signup endpoint. Accepts ProjectBearerAuth (JWT) or ApiKeyAuth (X-API-Key). 
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): ProjectBearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-add_custom_role_request = Mudbase::AddCustomRoleRequest.new({slug: 'rider', name: 'Delivery Rider', signup_endpoint: '/api/auth/local/signup/rider'}) # AddCustomRoleRequest | Custom role definition (slug, name, description, signupEndpoint, hierarchy, defaultPermissions).
-
-begin
-  # Add custom role
-  result = api_instance.add_custom_role(project_id, add_custom_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->add_custom_role: #{e}"
-end
-```
-
-#### Using the add_custom_role_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<UpdateMultiRoleSettings200Response>, Integer, Hash)> add_custom_role_with_http_info(project_id, add_custom_role_request)
-
-```ruby
-begin
-  # Add custom role
-  data, status_code, headers = api_instance.add_custom_role_with_http_info(project_id, add_custom_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <UpdateMultiRoleSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->add_custom_role_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **add_custom_role_request** | [**AddCustomRoleRequest**](AddCustomRoleRequest.md) | Custom role definition (slug, name, description, signupEndpoint, hierarchy, defaultPermissions). |  |
-
-### Return type
-
-[**UpdateMultiRoleSettings200Response**](UpdateMultiRoleSettings200Response.md)
-
-### Authorization
-
-[ProjectBearerAuth](../README.md#ProjectBearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
-## get_available_roles
-
-> <GetAvailableRoles200Response> get_available_roles(project_id)
-
-Get available roles for signup
-
-Get all available roles for user signup in a project. Accepts ProjectBearerAuth (JWT) or ApiKeyAuth (X-API-Key). 
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): ProjectBearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-
-begin
-  # Get available roles for signup
-  result = api_instance.get_available_roles(project_id)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->get_available_roles: #{e}"
-end
-```
-
-#### Using the get_available_roles_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<GetAvailableRoles200Response>, Integer, Hash)> get_available_roles_with_http_info(project_id)
-
-```ruby
-begin
-  # Get available roles for signup
-  data, status_code, headers = api_instance.get_available_roles_with_http_info(project_id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <GetAvailableRoles200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->get_available_roles_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-
-### Return type
-
-[**GetAvailableRoles200Response**](GetAvailableRoles200Response.md)
-
-### Authorization
-
-[ProjectBearerAuth](../README.md#ProjectBearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: application/json
-
-
-## get_multi_role_config
-
-> <GetMultiRoleConfig200Response> get_multi_role_config(project_id)
-
-Get multi-role feature configuration
-
-Get the ready-to-use multi-role system configuration for a project
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): ProjectBearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-
-begin
-  # Get multi-role feature configuration
-  result = api_instance.get_multi_role_config(project_id)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->get_multi_role_config: #{e}"
-end
-```
-
-#### Using the get_multi_role_config_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<GetMultiRoleConfig200Response>, Integer, Hash)> get_multi_role_config_with_http_info(project_id)
-
-```ruby
-begin
-  # Get multi-role feature configuration
-  data, status_code, headers = api_instance.get_multi_role_config_with_http_info(project_id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <GetMultiRoleConfig200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->get_multi_role_config_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-
-### Return type
-
-[**GetMultiRoleConfig200Response**](GetMultiRoleConfig200Response.md)
-
-### Authorization
-
-[ProjectBearerAuth](../README.md#ProjectBearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: application/json
-
-
-## oauth_signup_with_role
-
-> <LinkOAuthProvider200Response> oauth_signup_with_role(role, provider, project_id, opts)
-
-OAuth signup with specific role
-
-Public endpoint that initiates OAuth signup flow with a specific role assigned during registration. The OAuth provider must be configured and enabled for the project first. The role must be available for signup in the project's multi-role configuration. After successful OAuth authentication, the user will be created with the specified role. No authentication required - this is a public signup endpoint. 
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-role = 'vendor' # String | Role slug for signup (e.g. customer, vendor, seller).
-provider = 'google' # String | OAuth provider (e.g. google, github).
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-opts = {
-  redirect_url: 'https://client.app/auth/callback' # String | The URL to redirect to after authentication
-}
-
-begin
-  # OAuth signup with specific role
-  result = api_instance.oauth_signup_with_role(role, provider, project_id, opts)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->oauth_signup_with_role: #{e}"
-end
-```
-
-#### Using the oauth_signup_with_role_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<LinkOAuthProvider200Response>, Integer, Hash)> oauth_signup_with_role_with_http_info(role, provider, project_id, opts)
-
-```ruby
-begin
-  # OAuth signup with specific role
-  data, status_code, headers = api_instance.oauth_signup_with_role_with_http_info(role, provider, project_id, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <LinkOAuthProvider200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->oauth_signup_with_role_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **role** | **String** | Role slug for signup (e.g. customer, vendor, seller). |  |
-| **provider** | **String** | OAuth provider (e.g. google, github). |  |
-| **project_id** | **String** | Project ID. |  |
-| **redirect_url** | **String** | The URL to redirect to after authentication | [optional] |
-
-### Return type
-
-[**LinkOAuthProvider200Response**](LinkOAuthProvider200Response.md)
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: application/json
-
-
-## register_with_role
-
-> register_with_role(role, register_with_role_request)
-
-Register user with specific role (Local Auth)
-
-Public endpoint for user registration with a specific role. The role is specified in the URL path (e.g., /signup/customer, /signup/vendor). No authentication required - this is a public signup endpoint. 
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-role = 'customer' # String | Role slug for signup (e.g. customer, vendor).
-register_with_role_request = Mudbase::RegisterWithRoleRequest.new({email: 'email_example', password: 'password_example', first_name: 'first_name_example', last_name: 'last_name_example', project_id: 'project_id_example'}) # RegisterWithRoleRequest | Registration payload (email, password, firstName, lastName, projectId).
-
-begin
-  # Register user with specific role (Local Auth)
-  api_instance.register_with_role(role, register_with_role_request)
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->register_with_role: #{e}"
-end
-```
-
-#### Using the register_with_role_with_http_info variant
-
-This returns an Array which contains the response data (`nil` in this case), status code and headers.
-
-> <Array(nil, Integer, Hash)> register_with_role_with_http_info(role, register_with_role_request)
-
-```ruby
-begin
-  # Register user with specific role (Local Auth)
-  data, status_code, headers = api_instance.register_with_role_with_http_info(role, register_with_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => nil
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->register_with_role_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **role** | **String** | Role slug for signup (e.g. customer, vendor). |  |
-| **register_with_role_request** | [**RegisterWithRoleRequest**](RegisterWithRoleRequest.md) | Registration payload (email, password, firstName, lastName, projectId). |  |
-
-### Return type
-
-nil (empty response body)
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
-## toggle_role
-
-> <UpdateMultiRoleSettings200Response> toggle_role(project_id, role_slug, toggle_role_request)
-
-Toggle role on/off
-
-Enable or disable a role for the project. When disabled, the role is no longer available for signup or assignment.
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): ProjectBearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug to toggle (e.g. vendor, customer).
-toggle_role_request = Mudbase::ToggleRoleRequest.new({is_enabled: true}) # ToggleRoleRequest | Whether the role is enabled (true) or disabled (false).
-
-begin
-  # Toggle role on/off
-  result = api_instance.toggle_role(project_id, role_slug, toggle_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->toggle_role: #{e}"
-end
-```
-
-#### Using the toggle_role_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<UpdateMultiRoleSettings200Response>, Integer, Hash)> toggle_role_with_http_info(project_id, role_slug, toggle_role_request)
-
-```ruby
-begin
-  # Toggle role on/off
-  data, status_code, headers = api_instance.toggle_role_with_http_info(project_id, role_slug, toggle_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <UpdateMultiRoleSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->toggle_role_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **role_slug** | **String** | Role slug to toggle (e.g. vendor, customer). |  |
-| **toggle_role_request** | [**ToggleRoleRequest**](ToggleRoleRequest.md) | Whether the role is enabled (true) or disabled (false). |  |
-
-### Return type
-
-[**UpdateMultiRoleSettings200Response**](UpdateMultiRoleSettings200Response.md)
-
-### Authorization
-
-[ProjectBearerAuth](../README.md#ProjectBearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
-## update_collection_permissions
-
-> <UpdateMultiRoleSettings200Response> update_collection_permissions(project_id, role_slug, collection_id, update_collection_permissions_request)
-
-Update collection permissions for a role
-
-Update collection-specific permissions for a role in a project. Accepts ProjectBearerAuth (JWT) or ApiKeyAuth (X-API-Key). 
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): ProjectBearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug (e.g. vendor, customer).
-collection_id = '696ba6e4f4a9422ac4be4f74' # String | Collection ID to set permissions for.
-update_collection_permissions_request = Mudbase::UpdateCollectionPermissionsRequest.new # UpdateCollectionPermissionsRequest | Allowed actions and optional conditions for the role on this collection.
-
-begin
-  # Update collection permissions for a role
-  result = api_instance.update_collection_permissions(project_id, role_slug, collection_id, update_collection_permissions_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->update_collection_permissions: #{e}"
-end
-```
-
-#### Using the update_collection_permissions_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<UpdateMultiRoleSettings200Response>, Integer, Hash)> update_collection_permissions_with_http_info(project_id, role_slug, collection_id, update_collection_permissions_request)
-
-```ruby
-begin
-  # Update collection permissions for a role
-  data, status_code, headers = api_instance.update_collection_permissions_with_http_info(project_id, role_slug, collection_id, update_collection_permissions_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <UpdateMultiRoleSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->update_collection_permissions_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **role_slug** | **String** | Role slug (e.g. vendor, customer). |  |
-| **collection_id** | **String** | Collection ID to set permissions for. |  |
-| **update_collection_permissions_request** | [**UpdateCollectionPermissionsRequest**](UpdateCollectionPermissionsRequest.md) | Allowed actions and optional conditions for the role on this collection. |  |
-
-### Return type
-
-[**UpdateMultiRoleSettings200Response**](UpdateMultiRoleSettings200Response.md)
-
-### Authorization
-
-[ProjectBearerAuth](../README.md#ProjectBearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
-## update_multi_role_settings
-
-> <UpdateMultiRoleSettings200Response> update_multi_role_settings(project_id, update_multi_role_settings_request)
-
-Update multi-role feature settings
-
-Update multi-role feature settings for a project, including enabling/disabling the feature and configuring default roles. Accepts ProjectBearerAuth (JWT) or ApiKeyAuth (X-API-Key). 
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): ProjectBearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-update_multi_role_settings_request = Mudbase::UpdateMultiRoleSettingsRequest.new # UpdateMultiRoleSettingsRequest | Multi-role settings (e.g. isEnabled, defaultRole, allowMultipleRoles, requireApproval).
-
-begin
-  # Update multi-role feature settings
-  result = api_instance.update_multi_role_settings(project_id, update_multi_role_settings_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->update_multi_role_settings: #{e}"
-end
-```
-
-#### Using the update_multi_role_settings_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<UpdateMultiRoleSettings200Response>, Integer, Hash)> update_multi_role_settings_with_http_info(project_id, update_multi_role_settings_request)
-
-```ruby
-begin
-  # Update multi-role feature settings
-  data, status_code, headers = api_instance.update_multi_role_settings_with_http_info(project_id, update_multi_role_settings_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <UpdateMultiRoleSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->update_multi_role_settings_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **update_multi_role_settings_request** | [**UpdateMultiRoleSettingsRequest**](UpdateMultiRoleSettingsRequest.md) | Multi-role settings (e.g. isEnabled, defaultRole, allowMultipleRoles, requireApproval). |  |
-
-### Return type
-
-[**UpdateMultiRoleSettings200Response**](UpdateMultiRoleSettings200Response.md)
-
-### Authorization
-
-[ProjectBearerAuth](../README.md#ProjectBearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
-## update_project_role
-
-> <UpdateMultiRoleSettings200Response> update_project_role(project_id, role_slug, update_project_role_request)
-
-Update role configuration
-
-Update an existing role's metadata and requirements (name, description, hierarchy, approval/payment/KYC flags).
-
-### Examples
-
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): ProjectBearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = Mudbase::MultiRoleFeatureApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug to update (e.g. vendor, customer).
-update_project_role_request = Mudbase::UpdateProjectRoleRequest.new # UpdateProjectRoleRequest | Role fields to update (name, description, hierarchy, requiresApproval, requiresPayment, requiresKYC).
-
-begin
-  # Update role configuration
-  result = api_instance.update_project_role(project_id, role_slug, update_project_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->update_project_role: #{e}"
-end
-```
-
-#### Using the update_project_role_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<UpdateMultiRoleSettings200Response>, Integer, Hash)> update_project_role_with_http_info(project_id, role_slug, update_project_role_request)
-
-```ruby
-begin
-  # Update role configuration
-  data, status_code, headers = api_instance.update_project_role_with_http_info(project_id, role_slug, update_project_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <UpdateMultiRoleSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleFeatureApi->update_project_role_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **role_slug** | **String** | Role slug to update (e.g. vendor, customer). |  |
-| **update_project_role_request** | [**UpdateProjectRoleRequest**](UpdateProjectRoleRequest.md) | Role fields to update (name, description, hierarchy, requiresApproval, requiresPayment, requiresKYC). |  |
-
-### Return type
-
-[**UpdateMultiRoleSettings200Response**](UpdateMultiRoleSettings200Response.md)
-
-### Authorization
-
-[ProjectBearerAuth](../README.md#ProjectBearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-

data/docs/OauthCallback200Response.md

@@ -1,20 +0,0 @@
-# Mudbase::OauthCallback200Response
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **token** | **String** |  | [optional] |
-| **user** | [**User**](User.md) |  | [optional] |
-
-## Example
-
-```ruby
-require 'mudbase'
-
-instance = Mudbase::OauthCallback200Response.new(
-  token: null,
-  user: null
-)
-```
-

data/docs/OauthSignupWithRole400Response.md

@@ -1,20 +0,0 @@
-# Mudbase::OauthSignupWithRole400Response
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **error** | **String** |  | [optional] |
-| **message** | **String** |  | [optional] |
-
-## Example
-
-```ruby
-require 'mudbase'
-
-instance = Mudbase::OauthSignupWithRole400Response.new(
-  error: null,
-  message: null
-)
-```
-