vortex-python-sdk 0.9.1__tar.gz → 0.9.3__tar.gz

{vortex_python_sdk-0.9.1/src/vortex_python_sdk.egg-info → vortex_python_sdk-0.9.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vortex-python-sdk
-Version: 0.9.1
+Version: 0.9.3
 Summary: Vortex Python SDK for invitation management and JWT generation
 Author-email: TeamVortexSoftware <support@vortexsoftware.com>
 License-Expression: MIT
@@ -203,6 +203,46 @@ async def reinvite_user():
 invitation = vortex.reinvite_sync("invitation-id")
 ```
 
+#### 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.
+
+```python
+async def sync_internal_invitation_action():
+    # Async version
+    result = await vortex.sync_internal_invitation(
+        creator_id="user-123",      # The inviter's user ID in your system
+        target_value="user-456",    # The invitee's user ID in your system
+        action="accepted",          # "accepted" or "declined"
+        component_id="component-uuid"  # The widget component UUID
+    )
+    print(f"Processed: {result['processed']}")
+    print(f"Invitation IDs: {result['invitationIds']}")
+
+# Sync version
+result = vortex.sync_internal_invitation_sync(
+    creator_id="user-123",
+    target_value="user-456",
+    action="accepted",
+    component_id="component-uuid"
+)
+```
+
+**Parameters:**
+- `creator_id` (str) — The inviter's user ID in your system
+- `target_value` (str) — The invitee's user ID in your system
+- `action` ("accepted" | "declined") — The invitation decision
+- `component_id` (str) — The widget component UUID
+
+**Response:**
+- `processed` (int) — Count of invitations processed
+- `invitationIds` (list[str]) — 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
+
 ### Context Manager Usage
 
 ```python

{vortex_python_sdk-0.9.1 → vortex_python_sdk-0.9.3}/README.md

@@ -165,6 +165,46 @@ async def reinvite_user():
 invitation = vortex.reinvite_sync("invitation-id")
 ```
 
+#### 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.
+
+```python
+async def sync_internal_invitation_action():
+    # Async version
+    result = await vortex.sync_internal_invitation(
+        creator_id="user-123",      # The inviter's user ID in your system
+        target_value="user-456",    # The invitee's user ID in your system
+        action="accepted",          # "accepted" or "declined"
+        component_id="component-uuid"  # The widget component UUID
+    )
+    print(f"Processed: {result['processed']}")
+    print(f"Invitation IDs: {result['invitationIds']}")
+
+# Sync version
+result = vortex.sync_internal_invitation_sync(
+    creator_id="user-123",
+    target_value="user-456",
+    action="accepted",
+    component_id="component-uuid"
+)
+```
+
+**Parameters:**
+- `creator_id` (str) — The inviter's user ID in your system
+- `target_value` (str) — The invitee's user ID in your system
+- `action` ("accepted" | "declined") — The invitation decision
+- `component_id` (str) — The widget component UUID
+
+**Response:**
+- `processed` (int) — Count of invitations processed
+- `invitationIds` (list[str]) — 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
+
 ### Context Manager Usage
 
 ```python

{vortex_python_sdk-0.9.1 → vortex_python_sdk-0.9.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "vortex-python-sdk"
-version = "0.9.1"
+version = "0.9.3"
 description = "Vortex Python SDK for invitation management and JWT generation"
 authors = [{name = "TeamVortexSoftware", email = "support@vortexsoftware.com"}]
 readme = "README.md"

{vortex_python_sdk-0.9.1 → vortex_python_sdk-0.9.3/src/vortex_python_sdk.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vortex-python-sdk
-Version: 0.9.1
+Version: 0.9.3
 Summary: Vortex Python SDK for invitation management and JWT generation
 Author-email: TeamVortexSoftware <support@vortexsoftware.com>
 License-Expression: MIT
@@ -203,6 +203,46 @@ async def reinvite_user():
 invitation = vortex.reinvite_sync("invitation-id")
 ```
 
+#### 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.
+
+```python
+async def sync_internal_invitation_action():
+    # Async version
+    result = await vortex.sync_internal_invitation(
+        creator_id="user-123",      # The inviter's user ID in your system
+        target_value="user-456",    # The invitee's user ID in your system
+        action="accepted",          # "accepted" or "declined"
+        component_id="component-uuid"  # The widget component UUID
+    )
+    print(f"Processed: {result['processed']}")
+    print(f"Invitation IDs: {result['invitationIds']}")
+
+# Sync version
+result = vortex.sync_internal_invitation_sync(
+    creator_id="user-123",
+    target_value="user-456",
+    action="accepted",
+    component_id="component-uuid"
+)
+```
+
+**Parameters:**
+- `creator_id` (str) — The inviter's user ID in your system
+- `target_value` (str) — The invitee's user ID in your system
+- `action` ("accepted" | "declined") — The invitation decision
+- `component_id` (str) — The widget component UUID
+
+**Response:**
+- `processed` (int) — Count of invitations processed
+- `invitationIds` (list[str]) — 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
+
 ### Context Manager Usage
 
 ```python

{vortex_python_sdk-0.9.1 → vortex_python_sdk-0.9.3}/src/vortex_sdk/__init__.py

@@ -23,11 +23,13 @@ from .types import (
     InvitationResult,
     InvitationTarget,
     JwtPayload,
+    SyncInternalInvitationRequest,
+    SyncInternalInvitationResponse,
     VortexApiError,
 )
 from .vortex import Vortex
 
-__version__ = "0.7.0"
+__version__ = "0.9.2"
 __author__ = "TeamVortexSoftware"
 __email__ = "support@vortexsoftware.com"
 
@@ -48,6 +50,8 @@ __all__ = [
     "AutojoinDomain",
     "AutojoinDomainsResponse",
     "ConfigureAutojoinRequest",
+    "SyncInternalInvitationRequest",
+    "SyncInternalInvitationResponse",
     "ApiResponse",
     "ApiResponseJson",
     "ApiRequestBody",

{vortex_python_sdk-0.9.1 → vortex_python_sdk-0.9.3}/src/vortex_sdk/types.py

@@ -383,6 +383,26 @@ class AutojoinDomainsResponse(BaseModel):
         populate_by_name = True
 
 
+class SyncInternalInvitationRequest(BaseModel):
+    """Request body for syncing an internal invitation action"""
+    creator_id: str = Field(alias="creatorId")
+    target_value: str = Field(alias="targetValue")
+    action: Literal["accepted", "declined"]
+    component_id: str = Field(alias="componentId")
+
+    class Config:
+        populate_by_name = True
+
+
+class SyncInternalInvitationResponse(BaseModel):
+    """Response from syncing an internal invitation action"""
+    processed: int
+    invitation_ids: List[str] = Field(alias="invitationIds")
+
+    class Config:
+        populate_by_name = True
+
+
 class ConfigureAutojoinRequest(BaseModel):
     """Request body for configuring autojoin domains"""
     scope: str

{vortex_python_sdk-0.9.1 → vortex_python_sdk-0.9.3}/src/vortex_sdk/vortex.py

@@ -22,6 +22,8 @@ from .types import (
     Invitation,
     InvitationTarget,
     Inviter,
+    SyncInternalInvitationRequest,
+    SyncInternalInvitationResponse,
     User,
     VortexApiError,
 )
@@ -997,6 +999,85 @@ class Vortex:
         )
         return AutojoinDomainsResponse(**response)
 
+    async def sync_internal_invitation(
+        self,
+        creator_id: str,
+        target_value: str,
+        action: str,
+        component_id: str,
+    ) -> SyncInternalInvitationResponse:
+        """
+        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.
+
+        Args:
+            creator_id: The inviter's user ID
+            target_value: The invitee's user ID
+            action: The action taken: "accepted" or "declined"
+            component_id: The widget component UUID
+
+        Returns:
+            SyncInternalInvitationResponse with processed count and invitation_ids
+
+        Example:
+            result = await vortex.sync_internal_invitation(
+                creator_id="user-123",
+                target_value="user-456",
+                action="accepted",
+                component_id="component-uuid-789",
+            )
+            print(f"Processed {result.processed} invitations")
+        """
+        request = SyncInternalInvitationRequest(
+            creator_id=creator_id,
+            target_value=target_value,
+            action=action,
+            component_id=component_id,
+        )
+
+        response = await self._vortex_api_request(
+            "POST",
+            "/invitation-actions/sync-internal-invitation",
+            data=request.model_dump(by_alias=True),
+        )
+        return SyncInternalInvitationResponse(**response)
+
+    def sync_internal_invitation_sync(
+        self,
+        creator_id: str,
+        target_value: str,
+        action: str,
+        component_id: str,
+    ) -> SyncInternalInvitationResponse:
+        """
+        Sync an internal invitation action (accept or decline) (synchronous)
+
+        See sync_internal_invitation() for full documentation.
+
+        Example:
+            result = vortex.sync_internal_invitation_sync(
+                creator_id="user-123",
+                target_value="user-456",
+                action="accepted",
+                component_id="component-uuid-789",
+            )
+        """
+        request = SyncInternalInvitationRequest(
+            creator_id=creator_id,
+            target_value=target_value,
+            action=action,
+            component_id=component_id,
+        )
+
+        response = self._vortex_api_request_sync(
+            "POST",
+            "/invitation-actions/sync-internal-invitation",
+            data=request.model_dump(by_alias=True),
+        )
+        return SyncInternalInvitationResponse(**response)
+
     async def close(self) -> None:
         """Close the HTTP client"""
         await self._client.aclose()