vortex-ruby-sdk 1.8.2 → 1.8.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 68f5ea9102076ab25a0178aee43feb1a96f647709a634d0936b0d41da0b28a03
-  data.tar.gz: 347073bb4b8b3bb518e75b750112bb1ebc7230a1ef5507d1a0a1b4b3101745fa
+  metadata.gz: 677efb240644fe95c61d07a325952a6d2f8c6851eb14d59d17178d2c74881629
+  data.tar.gz: 83ad91fa108419346c2b6a707b62316573fdc5137d213a141840a599eca02dbe
 SHA512:
-  metadata.gz: 0ecc573608fc5df6bd8ad3dfac50f8b8bc91dd187a775558cd0837398620c85f3a14b3217e35da5845dabccc2ee2da0f71b8866726d963f221d7adde1ea61034
-  data.tar.gz: 7c1fe944df47039af93e32413c32522d535642df75bc1fbe5a8fe9b29c89d292459a590f14efec3e7015b373f66ccd7cf85b15b795165a390459bd144df7b961
+  metadata.gz: 324e85fc0660f7b952932a163ad10df4ae17f8f81dafd7c8eb6d8de70e771146474c0cc147d7643ae689f9629eafba0b9884c6f022b3091fb4147a3a1dc2f1eb
+  data.tar.gz: 2d780b17c5697ffcb0532bfcabce7756bd80a672b74417b5194e0c3e9089de31c0bc8c03977b4a0fdce0e416af1bb2a85868b2aa6050d2bf6a9fe9fbf7aa45e5

data/README.md

@@ -188,7 +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`
+- `POST /api/vortex/invitations/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

@@ -507,7 +507,7 @@ module Vortex
         componentId: component_id
       }
 
-      response = @connection.post('/api/v1/invitation-actions/sync-internal-invitation') do |req|
+      response = @connection.post('/api/v1/invitations/sync-internal-invitation') do |req|
         req.headers['Content-Type'] = 'application/json'
         req.body = JSON.generate(body)
       end

data/lib/vortex/version.rb

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

metadata

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