Create invitations

Two ways to invite someone onto an INVITE_ONLY tenant - pick based on whether you know the person’s email up front.

Token - tied to one email

const invite = await kerne.invitations.createToken({ email: '[email protected]' });
// { token, expiresAt, email }

Kerne emails the invite to that address as part of this call - there’s no separate send step. It expires in 7 days, not configurable. Calling this again for the same email replaces the previous unused invitation rather than stacking a second one.

Code - shareable, not tied to an email

const invite = await kerne.invitations.createCode({ maxUses: 25, expiresAt: '2027-01-01T00:00:00.000Z' });
// { code, expiresAt, maxUses }

code is an 8-character string Kerne generates (e.g. 7HK4RXPQ) - there’s no way to set your own. Nothing gets emailed: post it in your own onboarding flow, a Slack invite, wherever it needs to go. maxUses defaults to 1; omit expiresAt for a code that never expires. Both land the invitee on the same signup call, as invitationToken or invitationCode. Creating either requires your secret key, or a JWT owner crossing into their own tenant - never call these from a request an end user triggered themselves.

Server SDK

Frontend SDKs

Create invitations

Token - tied to one email

Code - shareable, not tied to an email

​Token - tied to one email

​Code - shareable, not tied to an email

Token - tied to one email

Code - shareable, not tied to an email