vortex-ruby-sdk 1.8.1 → 1.8.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '069cd5d8f962e84762ce56244a9775b16bdda20e5728fd05bdfff852d9483f16'
-  data.tar.gz: 105f2c1b8305730e1402b5049da2aaf3fd4e51e34f2e9801682537c8b72af331
+  metadata.gz: f18c676fb034bb528e9d15103c72c781336265ea591c207c98c3b43011999e19
+  data.tar.gz: f93d826ce67bbaf30a0d2c40240f0070c492f277823b9c377d31d0557b989d9f
 SHA512:
-  metadata.gz: 5bf887643c359e2768dbe35b130313a667fe201c02f90a490f3074ac0ed8c5e9797c44c61143cbfef49b0bcd6d2284a4e6e32fa2478d25dc862a11ea2f3de204
-  data.tar.gz: 486de49b074e29577b2ec1ba01d0d98b38b5df630cdbbeed3a98b460f4df2e5478979eed3aca66ce303d6a8fc008171ba02604d005b1721c2b2ad58c9069ac2b
+  metadata.gz: 55f270dd410709b262dded8417c3a0f76362e8650b4611a719cf4061601b0e2c056438c5ebe33f1d6544a2f6b41c22a341fd587ca9f93e97023920404401aec7
+  data.tar.gz: aefed295464f5b39ae39bd7738287f8e097b8ad5a1d4da056028019705f1a136856e4d63405a087d93bc268ddf0f27215ba19db53cd165caf833fc09b212785e

data/README.md

@@ -174,6 +174,7 @@ All methods match the functionality of other Vortex SDKs:
 - `get_invitations_by_group(group_type, group_id)` - Get group invitations
 - `delete_invitations_by_group(group_type, group_id)` - Delete group invitations
 - `reinvite(invitation_id)` - Reinvite user
+- `sync_internal_invitation(creator_id, target_value, action, component_id)` - Sync internal invitation action
 
 ## Route Structure
 
@@ -187,6 +188,39 @@ The SDK provides these routes (same as other SDKs for React provider compatibili
 - `GET /api/vortex/invitations/by-group/:type/:id`
 - `DELETE /api/vortex/invitations/by-group/:type/:id`
 - `POST /api/vortex/invitations/:id/reinvite`
+- `POST /api/vortex/invitation-actions/sync-internal-invitation`
+
+## Sync Internal Invitation
+
+If you're using `internal` delivery type invitations and managing the invitation flow within your own application, you can sync invitation decisions back to Vortex when users accept or decline invitations in your system.
+
+```ruby
+# Sync an internal invitation action
+result = client.sync_internal_invitation(
+  'user-123',           # creator_id - The inviter's user ID in your system
+  'user-456',           # target_value - The invitee's user ID in your system
+  'accepted',           # action - "accepted" or "declined"
+  'component-uuid'      # component_id - The widget component UUID
+)
+
+puts "Processed: #{result['processed']}"
+puts "Invitation IDs: #{result['invitationIds']}"
+```
+
+**Parameters:**
+- `creator_id` (String) — The inviter's user ID in your system
+- `target_value` (String) — The invitee's user ID in your system
+- `action` ("accepted" | "declined") — The invitation decision
+- `component_id` (String) — The widget component UUID
+
+**Response:**
+- `processed` (Integer) — Count of invitations processed
+- `invitationIds` (Array<String>) — IDs of processed invitations
+
+**Use cases:**
+- You handle invitation delivery through your own in-app notifications or UI
+- Users accept/decline invitations within your application
+- You need to keep Vortex updated with the invitation status
 
 ## JWT Payload Structure
 

data/lib/vortex/client.rb

@@ -479,6 +479,46 @@ module Vortex
       raise VortexError, "Failed to configure autojoin: #{e.message}"
     end
 
+    # Sync an internal invitation action (accept or decline)
+    #
+    # This method notifies Vortex that an internal invitation was accepted or declined
+    # within your application, so Vortex can update the invitation status accordingly.
+    #
+    # @param creator_id [String] The inviter's user ID
+    # @param target_value [String] The invitee's user ID
+    # @param action [String] The action taken: "accepted" or "declined"
+    # @param component_id [String] The widget component UUID
+    # @return [Hash] Response with :processed count and :invitationIds array
+    # @raise [VortexError] If the request fails
+    #
+    # @example
+    #   result = client.sync_internal_invitation(
+    #     'user-123',
+    #     'user-456',
+    #     'accepted',
+    #     'component-uuid-789'
+    #   )
+    #   puts "Processed #{result['processed']} invitations"
+    def sync_internal_invitation(creator_id, target_value, action, component_id)
+      body = {
+        creatorId: creator_id,
+        targetValue: target_value,
+        action: action,
+        componentId: component_id
+      }
+
+      response = @connection.post('/api/v1/invitation-actions/sync-internal-invitation') do |req|
+        req.headers['Content-Type'] = 'application/json'
+        req.body = JSON.generate(body)
+      end
+
+      handle_response(response)
+    rescue VortexError
+      raise
+    rescue => e
+      raise VortexError, "Failed to sync internal invitation: #{e.message}"
+    end
+
     private
 
     def build_connection

data/lib/vortex/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Vortex
-  VERSION = '1.8.1'
+  VERSION = '1.8.3'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vortex-ruby-sdk
 version: !ruby/object:Gem::Version
-  version: 1.8.1
+  version: 1.8.3
 platform: ruby
 authors:
 - Vortex Software
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-02-16 00:00:00.000000000 Z
+date: 2026-02-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday