curl --request GET \
--url https://api.example.com/api/v1/invitations/{invitationId} \
--header 'x-api-key: <api-key>'{
"id": "invitation-12345",
"accountId": "account-12345",
"attributes": {},
"clickThroughs": 5,
"configurationAttributes": {},
"createdAt": "2023-10-01T12:00:00Z",
"deactivated": false,
"deliveryCount": 3,
"deliveryTypes": [
"email",
"phone"
],
"foreignCreatorId": "creator-12345",
"invitationType": "single_use",
"modifiedAt": "2023-10-01T12:00:00Z",
"status": "queued",
"target": [
{
"type": "email",
"value": "foo@bar.com"
}
],
"views": 10,
"widgetConfigurationId": "widget-12345",
"deploymentId": "deployment-12345",
"projectId": "project-67890",
"groups": [
{
"type": "workspace",
"id": "workspace-12345",
"name": "Development Team"
}
],
"accepts": [
{
"id": "accept-12345",
"status": "accepted"
}
],
"scope": "6b366c56-c0a9-4689-b763-20c890481bc8",
"scopeType": "project",
"expired": false,
"source": "email",
"subtype": "pymk",
"expires": "2023-11-01T12:00:00Z",
"metadata": {
"customerId": "12345",
"source": "web"
},
"passThrough": "eyJhbGciOiJBMjU2R0NNIiwiZW5jIjoiQTI1NkdDTSJ9..."
}Fetch invitation details by invitation ID. Typically used during your acceptance flow, after parsing the invitation ID out of the URL when an invitee is redirected to your landing page.
curl --request GET \
--url https://api.example.com/api/v1/invitations/{invitationId} \
--header 'x-api-key: <api-key>'{
"id": "invitation-12345",
"accountId": "account-12345",
"attributes": {},
"clickThroughs": 5,
"configurationAttributes": {},
"createdAt": "2023-10-01T12:00:00Z",
"deactivated": false,
"deliveryCount": 3,
"deliveryTypes": [
"email",
"phone"
],
"foreignCreatorId": "creator-12345",
"invitationType": "single_use",
"modifiedAt": "2023-10-01T12:00:00Z",
"status": "queued",
"target": [
{
"type": "email",
"value": "foo@bar.com"
}
],
"views": 10,
"widgetConfigurationId": "widget-12345",
"deploymentId": "deployment-12345",
"projectId": "project-67890",
"groups": [
{
"type": "workspace",
"id": "workspace-12345",
"name": "Development Team"
}
],
"accepts": [
{
"id": "accept-12345",
"status": "accepted"
}
],
"scope": "6b366c56-c0a9-4689-b763-20c890481bc8",
"scopeType": "project",
"expired": false,
"source": "email",
"subtype": "pymk",
"expires": "2023-11-01T12:00:00Z",
"metadata": {
"customerId": "12345",
"source": "web"
},
"passThrough": "eyJhbGciOiJBMjU2R0NNIiwiZW5jIjoiQTI1NkdDTSJ9..."
}The ID of the invitation
The ID of the invitation
"invitation-12345"
The ID of the account associated with the invitation
"account-12345"
Various attributes of the invitation, none exist at the moment, but this acts as a placeholder for future use
The number of times the invitation has been clicked
5
The configuration attributes for the invitation. Includes raw data from widgets.
{}The date and time when the invitation was created
"2023-10-01T12:00:00Z"
Indicates whether the invitation has been deactivated
false
The number of times the invitation has been delivered. For example, for email invitations this would be the invitation email plus the total number of reminders the invitee received.
3
The types of delivery methods used for the invitation. Valid values: email, phone, share, internal
["email", "phone"]The inviter’s ID in your system.
"creator-12345"
The type of the invitation. A single_use invitation (e.g., email invitation) can only be accepted once. A multi_use invitation (e.g., shareable links) can be accepted multiple times. And autojoin allows people to join based on their email domain.
single_use, multi_use, autojoin "single_use"
The date and time when the invitation was last modified
"2023-10-01T12:00:00Z"
The current status of the invitation
queued, sending, delivered, accepted, shared, unfurled, accepted_elsewhere, sent "queued"
The target(s) for the invitation, such as email or phone
Show child attributes
[{ "type": "email", "value": "foo@bar.com" }]The number of times the invitation has been viewed
10
The ID of the widget configuration associated with the invitation
"widget-12345"
The ID of the deployment associated with the invitation
"deployment-12345"
The ID of the project associated with the invitation
"project-67890"
DEPRECATED: The groups associated with the invitation, such as workspaces or teams
Show child attributes
[
{
"type": "workspace",
"id": "workspace-12345",
"name": "Development Team"
}
]The acceptance details for the invitation
Show child attributes
[
{
"id": "accept-12345",
"status": "accepted"
}
]Defines the context for the invitation, and should be the ID in your system of the entity to which the invitation applies (e.g., workspace, org, etc.).
"6b366c56-c0a9-4689-b763-20c890481bc8"
The name of the entity that the ID passed in scope refers to (e.g., “workspace”, “organization”, “team”). Allows you to establish context for an invitation if you have multiple types of entities to which someone can be invited.
"project"
Indicates whether the invitation has expired based on the expiry configuration. Always false if the invitation has no expiry configured.
false
The source of the invitation (email, phone, internal, share, etc.)
"email"
Customer-defined subtype for categorizing this invitation (e.g., pymk, find-friends, profile-button)
"pymk"
The date and time when the invitation will expire or has expired. Only present if the invitation has an expiry configuration (expiryDays > 0).
"2023-11-01T12:00:00Z"
Information passed to Vortex on the metadata parameter in the client code when the invitation was created is returned here.
{ "customerId": "12345", "source": "web" }Encrypted passthrough data from the JWT, passed through without decryption. Can be used to securely pass context from the invitation creator to the acceptance flow.
"eyJhbGciOiJBMjU2R0NNIiwiZW5jIjoiQTI1NkdDTSJ9..."