vortex-ruby-sdk 1.8.2 → 1.8.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 68f5ea9102076ab25a0178aee43feb1a96f647709a634d0936b0d41da0b28a03
-  data.tar.gz: 347073bb4b8b3bb518e75b750112bb1ebc7230a1ef5507d1a0a1b4b3101745fa
+  metadata.gz: f18c676fb034bb528e9d15103c72c781336265ea591c207c98c3b43011999e19
+  data.tar.gz: f93d826ce67bbaf30a0d2c40240f0070c492f277823b9c377d31d0557b989d9f
 SHA512:
-  metadata.gz: 0ecc573608fc5df6bd8ad3dfac50f8b8bc91dd187a775558cd0837398620c85f3a14b3217e35da5845dabccc2ee2da0f71b8866726d963f221d7adde1ea61034
-  data.tar.gz: 7c1fe944df47039af93e32413c32522d535642df75bc1fbe5a8fe9b29c89d292459a590f14efec3e7015b373f66ccd7cf85b15b795165a390459bd144df7b961
+  metadata.gz: 55f270dd410709b262dded8417c3a0f76362e8650b4611a719cf4061601b0e2c056438c5ebe33f1d6544a2f6b41c22a341fd587ca9f93e97023920404401aec7
+  data.tar.gz: aefed295464f5b39ae39bd7738287f8e097b8ad5a1d4da056028019705f1a136856e4d63405a087d93bc268ddf0f27215ba19db53cd165caf833fc09b212785e

data/README.md

@@ -190,6 +190,38 @@ The SDK provides these routes (same as other SDKs for React provider compatibili
 - `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
 
 The SDK generates JWTs with the following payload structure:

data/lib/vortex/version.rb

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

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vortex-ruby-sdk
 version: !ruby/object:Gem::Version
-  version: 1.8.2
+  version: 1.8.3
 platform: ruby
 authors:
 - Vortex Software