mudbase 1.2.12 → 1.3.0

data/spec/api/chat_api_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MUDBASESDK
 
-#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 for fiat (platform subscriptions and 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) 
+#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: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.2.12
+The version of the OpenAPI document: 1.3.0
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0
@@ -32,199 +32,187 @@ describe 'ChatApi' do
     end
   end
 
-  # unit tests for chat_add_participant
+  # unit tests for add_participant
   # Add participant to chat
-  # Add a user to the chat with an optional role (admin or member).
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param chat_add_participant_request User ID to add and optional role (admin, member).
+  # @param project_id 
+  # @param chat_id 
+  # @param add_participant_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatAddParticipant200Response]
-  describe 'chat_add_participant test' do
+  # @return [AddParticipant200Response]
+  describe 'add_participant test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_add_reaction
+  # unit tests for add_reaction
   # Add reaction to message
-  # Add an emoji reaction to a message.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param message_id Message ID.
-  # @param chat_add_reaction_request Emoji reaction (e.g. 👍, ❤️).
+  # @param project_id 
+  # @param chat_id 
+  # @param message_id 
+  # @param add_reaction_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatAddReaction200Response]
-  describe 'chat_add_reaction test' do
+  # @return [AddReaction200Response]
+  describe 'add_reaction test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_create
+  # unit tests for create_chat
   # Create new chat
-  # Create a new chat (direct, group, channel, or broadcast) with name, type, participants, and optional settings.
-  # @param project_id Project ID.
-  # @param chat_create_request Chat name, type (direct/group/channel/broadcast), participants array, optional description and settings.
+  # @param project_id 
+  # @param create_chat_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatCreate201Response]
-  describe 'chat_create test' do
+  # @return [CreateChat201Response]
+  describe 'create_chat test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_delete_message
+  # unit tests for delete_message
   # Delete message
-  # Delete a message from the chat (sender or admin). May be soft-delete or permanent depending on implementation.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param message_id Message ID.
+  # @param project_id 
+  # @param chat_id 
+  # @param message_id 
   # @param [Hash] opts the optional parameters
   # @return [MessageResponse]
-  describe 'chat_delete_message test' do
+  describe 'delete_message test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_edit_message
+  # unit tests for edit_message
   # Edit message
-  # Update the content of a message (sender only; supports edit history).
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param message_id Message ID.
-  # @param chat_edit_message_request New plaintext content (non-E2EE messages) or new e2ee ciphertext (E2EE messages). One of content or e2ee.ciphertext is required.
+  # @param project_id 
+  # @param chat_id 
+  # @param message_id 
+  # @param edit_message_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatEditMessage200Response]
-  describe 'chat_edit_message test' do
+  # @return [EditMessage200Response]
+  describe 'edit_message test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_get
+  # unit tests for get_chat_details
   # Get chat details
-  # Returns full chat metadata including participants and roles for a single chat.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
+  # @param project_id 
+  # @param chat_id 
   # @param [Hash] opts the optional parameters
-  # @return [ChatGet200Response]
-  describe 'chat_get test' do
+  # @return [GetChatDetails200Response]
+  describe 'get_chat_details test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_get_chat_e2ee_participant_keys
+  # unit tests for get_chat_e2ee_participant_keys
   # List participant E2EE public keys
-  # Returns registered identity public keys for users in this chat (for client-side key distribution and encryption).
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
+  # Returns registered identity public keys for users in this chat (for client-side key distribution).
+  # @param project_id 
+  # @param chat_id 
   # @param [Hash] opts the optional parameters
-  # @return [ChatGetChatE2eeParticipantKeys200Response]
-  describe 'chat_get_chat_e2ee_participant_keys test' do
+  # @return [GetChatE2eeParticipantKeys200Response]
+  describe 'get_chat_e2ee_participant_keys test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_get_messages
+  # unit tests for get_chat_messages
   # Get chat messages
-  # Returns paginated messages for a chat with optional before/after cursor for time-based pagination.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
+  # @param project_id 
+  # @param chat_id 
   # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page Page number (1-based).
-  # @option opts [Integer] :limit Number of messages per page.
-  # @option opts [Time] :before Return messages before this timestamp (cursor).
-  # @option opts [Time] :after Return messages after this timestamp (cursor).
-  # @return [ChatGetMessages200Response]
-  describe 'chat_get_messages test' do
+  # @option opts [Integer] :page 
+  # @option opts [Integer] :limit 
+  # @option opts [Time] :before 
+  # @option opts [Time] :after 
+  # @return [GetChatMessages200Response]
+  describe 'get_chat_messages test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_list
+  # unit tests for get_user_chats
   # Get user chats
-  # Returns paginated list of chats for the current user in the project, with last message and unread count.
-  # @param project_id Project ID.
+  # @param project_id 
   # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page Page number (1-based).
-  # @option opts [Integer] :limit Number of chats per page.
-  # @return [ChatList200Response]
-  describe 'chat_list test' do
+  # @option opts [Integer] :page 
+  # @option opts [Integer] :limit 
+  # @return [GetUserChats200Response]
+  describe 'get_user_chats test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_mark_as_read
+  # unit tests for mark_messages_as_read
   # Mark messages as read
-  # Mark one or more messages as read for the current user in the chat.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param chat_mark_as_read_request Array of message IDs to mark as read.
+  # @param project_id 
+  # @param chat_id 
+  # @param mark_messages_as_read_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatMarkAsRead200Response]
-  describe 'chat_mark_as_read test' do
+  # @return [MarkMessagesAsRead200Response]
+  describe 'mark_messages_as_read test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_put_chat_e2ee_key
+  # unit tests for put_chat_e2ee_key
   # Register chat E2EE identity public key
-  # Stores your long-term public key for end-to-end encrypted chat (key agreement). Private keys never leave the client. Other participants use this to encrypt messages to you.
-  # @param project_id Project ID.
-  # @param chat_put_chat_e2ee_key_request Identity public key material for E2EE chat (base64). Private keys stay on the client.
+  # Stores your long-term public key for end-to-end encrypted chat (key agreement). Private keys never leave the client. Required for other participants to encrypt to you. 
+  # @param project_id 
+  # @param put_chat_e2ee_key_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatPutChatE2eeKey200Response]
-  describe 'chat_put_chat_e2ee_key test' do
+  # @return [PutChatE2eeKey200Response]
+  describe 'put_chat_e2ee_key test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_remove_participant
+  # unit tests for remove_participant
   # Remove participant from chat
-  # Remove a user from the chat by userId.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param chat_remove_participant_request User ID of the participant to remove.
+  # @param project_id 
+  # @param chat_id 
+  # @param remove_participant_request 
   # @param [Hash] opts the optional parameters
   # @return [MessageResponse]
-  describe 'chat_remove_participant test' do
+  describe 'remove_participant test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_remove_reaction
+  # unit tests for remove_reaction
   # Remove reaction from message
-  # Remove the current user&#39;s emoji reaction from a message.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param message_id Message ID.
-  # @param chat_add_reaction_request Emoji to remove (must match the reaction added by the user).
+  # @param project_id 
+  # @param chat_id 
+  # @param message_id 
+  # @param add_reaction_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatRemoveReaction200Response]
-  describe 'chat_remove_reaction test' do
+  # @return [RemoveReaction200Response]
+  describe 'remove_reaction test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for chat_send_message
+  # unit tests for send_message
   # Send message
-  # Send a message (text, image, video, audio, file, location, contact) to a chat with optional replyTo and mentions. For end-to-end encryption, use type&#x3D;text with e2ee.ciphertext (base64) instead of plaintext content; server stores ciphertext only.
-  # @param project_id Project ID.
-  # @param chat_id Chat ID.
-  # @param chat_send_message_request Message type and content, or E2EE ciphertext for text messages. Plaintext requires content; E2EE requires type&#x3D;text and e2ee.ciphertext (omit plaintext content).
+  # @param project_id 
+  # @param chat_id 
+  # @param send_message_request 
   # @param [Hash] opts the optional parameters
-  # @return [ChatSendMessage201Response]
-  describe 'chat_send_message test' do
+  # @return [SendMessage201Response]
+  describe 'send_message test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/collections_api_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MUDBASESDK
 
-#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 for fiat (platform subscriptions and 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) 
+#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: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.2.12
+The version of the OpenAPI document: 1.3.0
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0
@@ -32,66 +32,66 @@ describe 'CollectionsApi' do
     end
   end
 
-  # unit tests for collections_create
+  # unit tests for create_collection
   # Create new collection
-  # Create a new collection in a project. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param create_collection_request Collection name, optional slug, fields, permissions, and settings.
+  # Create a new collection in a project. Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
+  # @param create_collection_request 
   # @param [Hash] opts the optional parameters
-  # @return [CollectionsCreate201Response]
-  describe 'collections_create test' do
+  # @return [CreateCollection201Response]
+  describe 'create_collection test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for collections_delete
+  # unit tests for delete_collection
   # Delete collection
-  # Delete a collection permanently. This is a destructive operation. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
+  # Delete a collection permanently. This is a destructive operation. Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
+  # @param collection_id 
   # @param [Hash] opts the optional parameters
   # @return [MessageResponse]
-  describe 'collections_delete test' do
+  describe 'delete_collection test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for collections_get
+  # unit tests for get_collection
   # Get single collection
-  # Get collection details by ID. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
+  # Get collection details by ID. Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
+  # @param collection_id 
   # @param [Hash] opts the optional parameters
   # @return [Collection]
-  describe 'collections_get test' do
+  describe 'get_collection test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for collections_list
+  # unit tests for list_collections
   # List collections in project
-  # List all collections in a project. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
+  # List all collections in a project. Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
   # @param [Hash] opts the optional parameters
-  # @return [CollectionsList200Response]
-  describe 'collections_list test' do
+  # @return [ListCollections200Response]
+  describe 'list_collections test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for collections_update
+  # unit tests for update_collection
   # Update collection
-  # Update collection configuration (name, fields, permissions). Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
-  # @param update_collection_request Fields to update (name, fields, permissions, settings).
+  # Update collection configuration (name, fields, permissions). Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
+  # @param collection_id 
+  # @param update_collection_request 
   # @param [Hash] opts the optional parameters
-  # @return [CollectionsCreate201Response]
-  describe 'collections_update test' do
+  # @return [CreateCollection201Response]
+  describe 'update_collection test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/compliance_api_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MUDBASESDK
 
-#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 for fiat (platform subscriptions and 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) 
+#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: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.2.12
+The version of the OpenAPI document: 1.3.0
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0
@@ -32,13 +32,71 @@ describe 'ComplianceApi' do
     end
   end
 
-  # unit tests for compliance_log_security_event
+  # unit tests for api_gdpr_erase_post
+  # Erase my personal data (GDPR Art. 17)
+  # Anonymizes the subject&#39;s PII, revokes sessions/tokens, and anonymizes (never hard-deletes) financial/legal-retention records. Idempotent and self-scoped.  Requires re-proving your current password (skipped only for OAuth-only accounts with no password set) and, if 2FA is enabled, a fresh TOTP code - the same step-up re-authentication already required by the less-destructive &#x60;PATCH /api/users/password&#x60; and &#x60;POST /api/users/2fa/disable&#x60;. 
+  # @param api_gdpr_erase_post_request 
+  # @param [Hash] opts the optional parameters
+  # @return [ApplyRoleFeaturePreset200Response]
+  describe 'api_gdpr_erase_post test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for api_gdpr_export_get
+  # Export my personal data (GDPR Art. 15)
+  # Returns the authenticated subject&#39;s personal data as a downloadable JSON attachment. Self-scoped — a caller can only export their own data.
+  # @param [Hash] opts the optional parameters
+  # @return [Object]
+  describe 'api_gdpr_export_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for generate_access_review
+  # Generate access review report (SOC 2)
+  # Generate access review report for compliance audits (SOC 2, ISO 27001, etc.). Requires JWT Bearer token authentication. Both OrgBearerAuth and ProjectBearerAuth are supported (they use the same JWT token format). These are organization-level operations. 
+  # @param generate_access_review_request 
+  # @param [Hash] opts the optional parameters
+  # @return [GenerateAccessReview200Response]
+  describe 'generate_access_review test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for generate_data_processing_record
+  # Generate data processing record (GDPR Article 30)
+  # Generate GDPR Article 30 compliant data processing record
+  # @param generate_data_processing_record_request 
+  # @param [Hash] opts the optional parameters
+  # @return [GenerateDataProcessingRecord200Response]
+  describe 'generate_data_processing_record test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_compliance_summary
+  # Get compliance summary
+  # Get compliance dashboard data (GDPR, SOC 2, security status). Requires JWT Bearer token authentication. Both OrgBearerAuth and ProjectBearerAuth are supported (they use the same JWT token format). These are organization-level operations.
+  # @param [Hash] opts the optional parameters
+  # @return [GetComplianceSummary200Response]
+  describe 'get_compliance_summary test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for log_security_event
   # Log security event
-  # Log a security event for compliance and audit (e.g. SOC 2, GDPR). Event type and severity are required; optional details (userId, resource, ipAddress, etc.) for forensics.
-  # @param compliance_log_security_event_request Event type (e.g. unauthorized_access_attempt, brute_force_attempt), severity (low–critical), and optional details object for context.
+  # Log a security event for compliance and audit purposes
+  # @param log_security_event_request 
   # @param [Hash] opts the optional parameters
-  # @return [ComplianceLogSecurityEvent200Response]
-  describe 'compliance_log_security_event test' do
+  # @return [LogSecurityEvent200Response]
+  describe 'log_security_event test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/data_api_spec.rb

@@ -1,9 +1,9 @@
 =begin
 #MUDBASESDK
 
-#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 for fiat (platform subscriptions and 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) 
+#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: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.2.12
+The version of the OpenAPI document: 1.3.0
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0
@@ -32,75 +32,73 @@ describe 'DataApi' do
     end
   end
 
-  # unit tests for data_create
+  # unit tests for create_data
   # Create data in collection
-  # Create a new document in a collection. Request body must match the collection schema. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
-  # @param body Document fields matching the collection schema.
+  # @param project_id 
+  # @param collection_id 
+  # @param body 
   # @param [Hash] opts the optional parameters
   # @return [DataResponse]
-  describe 'data_create test' do
+  describe 'create_data test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for data_delete
+  # unit tests for delete_data
   # Delete document
-  # Delete a document from a collection. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
-  # @param document_id Document ID.
+  # Delete a document from a collection. Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
+  # @param collection_id 
+  # @param document_id 
   # @param [Hash] opts the optional parameters
   # @return [MessageResponse]
-  describe 'data_delete test' do
+  describe 'delete_data test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for data_get
+  # unit tests for get_data
   # Get single document
-  # Get a document by ID from a collection. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
-  # @param document_id Document ID.
+  # @param project_id 
+  # @param collection_id 
+  # @param document_id 
   # @param [Hash] opts the optional parameters
   # @return [DataResponse]
-  describe 'data_get test' do
+  describe 'get_data test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for data_list
+  # unit tests for list_data
   # List data in collection
-  # List all documents in a collection with optional pagination, sort, and filter. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
+  # List all documents in a collection. Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
+  # @param collection_id 
   # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page Page number (1-based).
-  # @option opts [Integer] :limit Number of documents per page.
-  # @option opts [String] :sort Sort field and order (e.g. -createdAt, name).
-  # @option opts [String] :filter JSON string for filtering documents (e.g. {\&quot;status\&quot;:\&quot;active\&quot;}).
+  # @option opts [Integer] :page 
+  # @option opts [Integer] :limit 
+  # @option opts [String] :sort 
+  # @option opts [String] :filter 
   # @return [DataListResponse]
-  describe 'data_list test' do
+  describe 'list_data test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for data_update
+  # unit tests for update_data
   # Update document
-  # Update a document in a collection. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
-  # @param project_id Project ID.
-  # @param collection_id Collection ID.
-  # @param document_id Document ID.
-  # @param body Partial document fields to update.
+  # Update a document in a collection. Accepts: OrgBearerAuth (for admin users), ProjectBearerAuth (JWT for authenticated users), or ApiKeyAuth (X-API-Key for programmatic access). Both ProjectBearerAuth and ApiKeyAuth are fully implemented. 
+  # @param project_id 
+  # @param collection_id 
+  # @param document_id 
+  # @param body 
   # @param [Hash] opts the optional parameters
   # @return [DataResponse]
-  describe 'data_update test' do
+  describe 'update_data test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end