curl --request POST \
--url https://api.example.com/api/v1/invitations/sync-internal-invitation \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"creatorId": "user-12345",
"targetValue": "user-67890",
"action": "accepted",
"componentId": "123e4567-e89b-12d3-a456-426614174000"
}
'{
"processed": 1,
"invitationIds": [
"invitation-12345"
]
}This endpoint allows customers with their own internal invitation system to sync invitation decisions back to Vortex.
When an invitee accepts or declines an invitation in the customer’s system, they can call this endpoint to update the corresponding Vortex invitation.
The lookup is performed by matching:
Only pending internal invitations are matched. If accepted, the invitation is marked as accepted. If declined, the invitation is deactivated.
curl --request POST \
--url https://api.example.com/api/v1/invitations/sync-internal-invitation \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"creatorId": "user-12345",
"targetValue": "user-67890",
"action": "accepted",
"componentId": "123e4567-e89b-12d3-a456-426614174000"
}
'{
"processed": 1,
"invitationIds": [
"invitation-12345"
]
}The ID of the user who created the invitation in your system
"user-12345"
The ID of the user who received the invitation (the invitee) in your system
"user-67890"
The action to perform on the invitation
accepted, declined "accepted"
The ID of the component (widget) associated with the invitation
"123e4567-e89b-12d3-a456-426614174000"