@teamvortexsoftware/vortex-fastify-5-sdk 0.4.1 → 0.4.2

package/README.md

@@ -294,6 +294,33 @@ const { invitations } = await response.json();
 await fetch(`/api/vortex/invitations/${invitationId}`, { method: 'DELETE' });
 ```
 
+### 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.
+
+```typescript
+// Sync an internal invitation action (accept or decline)
+const response = await fetch('/api/vortex/invitation-actions/sync-internal-invitation', {
+  method: 'POST',
+  headers: { 'Content-Type': 'application/json' },
+  body: JSON.stringify({
+    creatorId: 'user-123',      // The inviter's user ID in your system
+    targetValue: 'user-456',    // The invitee's user ID in your system
+    action: 'accepted',         // "accepted" or "declined"
+    componentId: 'component-uuid' // The widget component UUID
+  })
+});
+
+const result = await response.json();
+// result.processed - Number of invitations processed
+// result.invitationIds - Array of processed invitation IDs
+```
+
+**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
+
 ## 🚀 Fastify-Specific Features
 
 ### Plugin Architecture

package/package.json

@@ -2,7 +2,7 @@
   "name": "@teamvortexsoftware/vortex-fastify-5-sdk",
   "description": "Drop-in Fastify module for Vortex API integration",
   "author": "@teamvortexsoftware",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "exports": {
@@ -38,7 +38,7 @@
     "typescript-eslint": "8.50.1"
   },
   "dependencies": {
-    "@teamvortexsoftware/vortex-node-22-sdk": "^0.8.2"
+    "@teamvortexsoftware/vortex-node-22-sdk": "^0.8.3"
   },
   "peerDependencies": {
     "fastify": ">=5.0.0"