RubyGems - mudbase - Versions diffs - 1.2.7 → 1.2.9 - Mend

mudbase 1.2.7 → 1.2.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (693) hide show

checksums.yaml CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a96d489fdf940401487d8797231921d64c6ccffdcabd1c2b857d84cb37b6bbdd
-  data.tar.gz: db95c781b6ab4d9cd009e8d0e4282bcbda8aa2ff5e00966a8763ecbd73590360
+  metadata.gz: b2805e27a5498e116fecba0b9b6b9b845b04d4ee3c04ca4b0d71cbf22b9c71e8
+  data.tar.gz: aee4e046ca3ca886428a344ae5d358b149b93fc8962d8a44bb7d290a49604e61
 SHA512:
-  metadata.gz: d3fd54f17f350a5371b8b1b9dbc01c23a47824ab041f8e454b399997916fc5e9efc2635b841d3768f122287a518922a5078797172903c3559d98b537f1a4d5be
-  data.tar.gz: da7ad1fca111b9aa7e8813928e3e385eb24e86cee2991ab09ff0c07d18e8d6a4111a72dceac8006bd1f338bfda6bf9b64b1e5c226dc608a6bf2f0621b39b1013
+  metadata.gz: 66acfa9da5d38bc441ab0e3bf569506c62b73113ea54aa0ea9e3b7c0966ddc9e003be66feaffe0bd43f6add20efbe468f25c07e355c191fb5dd659de199291ad
+  data.tar.gz: d6bd2472c0a605caa5477e838bf2f396426ec243ddf3010da198e8555954cafc40813407c8ceba89652b8301cc0721dc40084c08d80a3bbebc7b7b8561e6d93e

data/docs/MultiRoleApi.md CHANGED Viewed

@@ -6,13 +6,6 @@ All URIs are relative to *https://cloud.mudbase.dev*
 | ------ | ------------ | ----------- |
 | [**auth_oauth_signup_with_role**](MultiRoleApi.md#auth_oauth_signup_with_role) | **GET** /api/auth/oauth/signup/{role}/{provider}/{projectId} | OAuth signup with specific role |
 | [**auth_register_with_role**](MultiRoleApi.md#auth_register_with_role) | **POST** /api/auth/local/signup/{role} | Register user with specific role (Local Auth) |
-| [**multi_role_add_role**](MultiRoleApi.md#multi_role_add_role) | **POST** /api/projects/{projectId}/multi-role/roles | Add custom role |
-| [**multi_role_get_available_roles**](MultiRoleApi.md#multi_role_get_available_roles) | **GET** /api/projects/{projectId}/multi-role/roles/available | Get available roles for signup |
-| [**multi_role_get_config**](MultiRoleApi.md#multi_role_get_config) | **GET** /api/projects/{projectId}/multi-role | Get multi-role feature configuration |
-| [**multi_role_toggle_role**](MultiRoleApi.md#multi_role_toggle_role) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug}/toggle | Toggle role on/off |
-| [**multi_role_update_collection_permissions**](MultiRoleApi.md#multi_role_update_collection_permissions) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug}/collections/{collectionId}/permissions | Update collection permissions for a role |
-| [**multi_role_update_role**](MultiRoleApi.md#multi_role_update_role) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug} | Update role configuration |
-| [**multi_role_update_settings**](MultiRoleApi.md#multi_role_update_settings) | **PATCH** /api/projects/{projectId}/multi-role/settings | Update multi-role feature settings |
 ## auth_oauth_signup_with_role
@@ -30,7 +23,7 @@ require 'time'
 require 'mudbase'
 api_instance = Mudbase::MultiRoleApi.new
-role = 'vendor' # String | Role slug for signup (e.g. customer, vendor, seller).
+role = 'customer' # String | Path segment must match the role's `signupEndpoint` (default `customer`; use each role's configured endpoint).
 provider = 'google' # String | OAuth provider (e.g. google, github).
 project_id = '685ad30be129932fbb7a1047' # String | Project ID.
 opts = {
@@ -68,7 +61,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **role** | **String** | Role slug for signup (e.g. customer, vendor, seller). |  |
+| **role** | **String** | Path segment must match the role&#39;s &#x60;signupEndpoint&#x60; (default &#x60;customer&#x60;; use each role&#39;s configured endpoint). |  |
 | **provider** | **String** | OAuth provider (e.g. google, github). |  |
 | **project_id** | **String** | Project ID. |  |
 | **redirect_url** | **String** | The URL to redirect to after authentication | [optional] |
@@ -93,7 +86,7 @@ No authorization required
 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.
+Public endpoint for user registration with a specific role. The path segment must match a role's `signupEndpoint` (default starter is `customer`; add more roles via multi-role API). No authentication required - this is a public signup endpoint.
 ### Examples
@@ -102,7 +95,7 @@ require 'time'
 require 'mudbase'
 api_instance = Mudbase::MultiRoleApi.new
-role = 'customer' # String | Role slug for signup (e.g. customer, vendor).
+role = 'customer' # String | Must match the role's `signupEndpoint` (default `customer`; other values for roles you add).
 auth_register_with_role_request = Mudbase::AuthRegisterWithRoleRequest.new({email: 'email_example', password: 'password_example', first_name: 'first_name_example', last_name: 'last_name_example', project_id: 'project_id_example'}) # AuthRegisterWithRoleRequest | Registration payload (email, password, firstName, lastName, projectId).
 begin
@@ -135,7 +128,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **role** | **String** | Role slug for signup (e.g. customer, vendor). |  |
+| **role** | **String** | Must match the role&#39;s &#x60;signupEndpoint&#x60; (default &#x60;customer&#x60;; other values for roles you add). |  |
 | **auth_register_with_role_request** | [**AuthRegisterWithRoleRequest**](AuthRegisterWithRoleRequest.md) | Registration payload (email, password, firstName, lastName, projectId). |  |
 ### Return type
@@ -151,504 +144,3 @@ No authorization required
 - **Content-Type**: application/json
 - **Accept**: application/json
-## multi_role_add_role
-> <MultiRoleUpdateSettings200Response> multi_role_add_role(project_id, multi_role_add_role_request)
-Add custom role
-Add a custom role to a project with specific permissions and signup endpoint. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key).
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-multi_role_add_role_request = Mudbase::MultiRoleAddRoleRequest.new({slug: 'rider', name: 'Delivery Rider', signup_endpoint: '/api/auth/local/signup/rider'}) # MultiRoleAddRoleRequest | Custom role definition (slug, name, description, signupEndpoint, hierarchy, defaultPermissions).
-begin
-  # Add custom role
-  result = api_instance.multi_role_add_role(project_id, multi_role_add_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_add_role: #{e}"
-end
-```
-#### Using the multi_role_add_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_add_role_with_http_info(project_id, multi_role_add_role_request)
-```ruby
-begin
-  # Add custom role
-  data, status_code, headers = api_instance.multi_role_add_role_with_http_info(project_id, multi_role_add_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_add_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **multi_role_add_role_request** | [**MultiRoleAddRoleRequest**](MultiRoleAddRoleRequest.md) | Custom role definition (slug, name, description, signupEndpoint, hierarchy, defaultPermissions). |  |
-### Return type
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_get_available_roles
-> <MultiRoleGetAvailableRoles200Response> multi_role_get_available_roles(project_id)
-Get available roles for signup
-Get all available roles for user signup in a project. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key).
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-begin
-  # Get available roles for signup
-  result = api_instance.multi_role_get_available_roles(project_id)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_available_roles: #{e}"
-end
-```
-#### Using the multi_role_get_available_roles_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleGetAvailableRoles200Response>, Integer, Hash)> multi_role_get_available_roles_with_http_info(project_id)
-```ruby
-begin
-  # Get available roles for signup
-  data, status_code, headers = api_instance.multi_role_get_available_roles_with_http_info(project_id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleGetAvailableRoles200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_available_roles_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-### Return type
-[**MultiRoleGetAvailableRoles200Response**](MultiRoleGetAvailableRoles200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json
-## multi_role_get_config
-> <MultiRoleGetConfig200Response> multi_role_get_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): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-begin
-  # Get multi-role feature configuration
-  result = api_instance.multi_role_get_config(project_id)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_config: #{e}"
-end
-```
-#### Using the multi_role_get_config_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleGetConfig200Response>, Integer, Hash)> multi_role_get_config_with_http_info(project_id)
-```ruby
-begin
-  # Get multi-role feature configuration
-  data, status_code, headers = api_instance.multi_role_get_config_with_http_info(project_id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleGetConfig200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_config_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-### Return type
-[**MultiRoleGetConfig200Response**](MultiRoleGetConfig200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json
-## multi_role_toggle_role
-> <MultiRoleUpdateSettings200Response> multi_role_toggle_role(project_id, role_slug, multi_role_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): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug to toggle (e.g. vendor, customer).
-multi_role_toggle_role_request = Mudbase::MultiRoleToggleRoleRequest.new({is_enabled: true}) # MultiRoleToggleRoleRequest | Whether the role is enabled (true) or disabled (false).
-begin
-  # Toggle role on/off
-  result = api_instance.multi_role_toggle_role(project_id, role_slug, multi_role_toggle_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_toggle_role: #{e}"
-end
-```
-#### Using the multi_role_toggle_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_toggle_role_with_http_info(project_id, role_slug, multi_role_toggle_role_request)
-```ruby
-begin
-  # Toggle role on/off
-  data, status_code, headers = api_instance.multi_role_toggle_role_with_http_info(project_id, role_slug, multi_role_toggle_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_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). |  |
-| **multi_role_toggle_role_request** | [**MultiRoleToggleRoleRequest**](MultiRoleToggleRoleRequest.md) | Whether the role is enabled (true) or disabled (false). |  |
-### Return type
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_update_collection_permissions
-> <MultiRoleUpdateSettings200Response> multi_role_update_collection_permissions(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
-Update collection permissions for a role
-Update collection-specific permissions for a role in a project. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key).
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.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.
-multi_role_update_collection_permissions_request = Mudbase::MultiRoleUpdateCollectionPermissionsRequest.new # MultiRoleUpdateCollectionPermissionsRequest | Allowed actions and optional conditions for the role on this collection.
-begin
-  # Update collection permissions for a role
-  result = api_instance.multi_role_update_collection_permissions(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_collection_permissions: #{e}"
-end
-```
-#### Using the multi_role_update_collection_permissions_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_update_collection_permissions_with_http_info(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
-```ruby
-begin
-  # Update collection permissions for a role
-  data, status_code, headers = api_instance.multi_role_update_collection_permissions_with_http_info(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_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. |  |
-| **multi_role_update_collection_permissions_request** | [**MultiRoleUpdateCollectionPermissionsRequest**](MultiRoleUpdateCollectionPermissionsRequest.md) | Allowed actions and optional conditions for the role on this collection. |  |
-### Return type
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_update_role
-> <MultiRoleUpdateSettings200Response> multi_role_update_role(project_id, role_slug, multi_role_update_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): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug to update (e.g. vendor, customer).
-multi_role_update_role_request = Mudbase::MultiRoleUpdateRoleRequest.new # MultiRoleUpdateRoleRequest | Role fields to update (name, description, hierarchy, requiresApproval, requiresPayment, requiresKYC).
-begin
-  # Update role configuration
-  result = api_instance.multi_role_update_role(project_id, role_slug, multi_role_update_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_role: #{e}"
-end
-```
-#### Using the multi_role_update_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_update_role_with_http_info(project_id, role_slug, multi_role_update_role_request)
-```ruby
-begin
-  # Update role configuration
-  data, status_code, headers = api_instance.multi_role_update_role_with_http_info(project_id, role_slug, multi_role_update_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_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). |  |
-| **multi_role_update_role_request** | [**MultiRoleUpdateRoleRequest**](MultiRoleUpdateRoleRequest.md) | Role fields to update (name, description, hierarchy, requiresApproval, requiresPayment, requiresKYC). |  |
-### Return type
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_update_settings
-> <MultiRoleUpdateSettings200Response> multi_role_update_settings(project_id, multi_role_update_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 BearerToken (JWT) or ApiKeyAuth (X-API-Key).
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-multi_role_update_settings_request = Mudbase::MultiRoleUpdateSettingsRequest.new # MultiRoleUpdateSettingsRequest | Multi-role settings (e.g. isEnabled, defaultRole, allowMultipleRoles, requireApproval).
-begin
-  # Update multi-role feature settings
-  result = api_instance.multi_role_update_settings(project_id, multi_role_update_settings_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_settings: #{e}"
-end
-```
-#### Using the multi_role_update_settings_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_update_settings_with_http_info(project_id, multi_role_update_settings_request)
-```ruby
-begin
-  # Update multi-role feature settings
-  data, status_code, headers = api_instance.multi_role_update_settings_with_http_info(project_id, multi_role_update_settings_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_settings_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **multi_role_update_settings_request** | [**MultiRoleUpdateSettingsRequest**](MultiRoleUpdateSettingsRequest.md) | Multi-role settings (e.g. isEnabled, defaultRole, allowMultipleRoles, requireApproval). |  |
-### Return type
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json

data/docs/RoleElevationApi.md CHANGED Viewed

@@ -103,7 +103,7 @@ end
 api_instance = Mudbase::RoleElevationApi.new
 project_id = 'project_id_example' # String | Project ID.
-role_elevation_request_request = Mudbase::RoleElevationRequestRequest.new({role_slug: 'vendor'}) # RoleElevationRequestRequest | Role slug to request elevation to (e.g. vendor).
+role_elevation_request_request = Mudbase::RoleElevationRequestRequest.new({role_slug: 'seller'}) # RoleElevationRequestRequest | Role slug to request elevation to (e.g. a higher-privilege role you configured).
 begin
   # Request role elevation
@@ -137,7 +137,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **project_id** | **String** | Project ID. |  |
-| **role_elevation_request_request** | [**RoleElevationRequestRequest**](RoleElevationRequestRequest.md) | Role slug to request elevation to (e.g. vendor). |  |
+| **role_elevation_request_request** | [**RoleElevationRequestRequest**](RoleElevationRequestRequest.md) | Role slug to request elevation to (e.g. a higher-privilege role you configured). |  |
 ### Return type

data/docs/RoleElevationRequestRequest.md CHANGED Viewed

@@ -12,7 +12,7 @@
 require 'mudbase'
 instance = Mudbase::RoleElevationRequestRequest.new(
-  role_slug: vendor
+  role_slug: seller
 )
 ```

data/lib/mudbase/api/auth_api.rb CHANGED Viewed

@@ -3,7 +3,7 @@
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API)
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.9
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/billing_api.rb CHANGED Viewed

@@ -3,7 +3,7 @@
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API)
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.9
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/chat_api.rb CHANGED Viewed

@@ -3,7 +3,7 @@
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API)
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.9
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/collections_api.rb CHANGED Viewed

@@ -3,7 +3,7 @@
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API)
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.9
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/compliance_api.rb CHANGED Viewed

@@ -3,7 +3,7 @@
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API)
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.9
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/data_api.rb CHANGED Viewed

@@ -3,7 +3,7 @@
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API)
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.9
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/functions_api.rb CHANGED Viewed

@@ -3,7 +3,7 @@
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API)
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.9
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0