v1
Personnel
Personnel

Send Invite Link

Deliver an OUTSTANDING WorkOS invitation over a second channel.

WorkOS reports an invitation as pending whether the email was delivered, bounced, or never left - there is no delivery field in the API or the dashboard. So a person whose mail server drops it is simply stuck, and no one can tell that apart from someone who has not got round to clicking. This resends the SAME invitation link by SMS or from our own SMTP, which fails independently of whoever WorkOS sends through.

It does NOT mint a new invitation. resend_invite is the endpoint for that; this one only re-delivers what is already outstanding, so the link in the original email keeps working and the two cannot diverge.

THE CALLER DOES NOT CHOOSE THE DESTINATION. Phone and email come off the person's own record, never off the request. That is deliberate: the invitation link is a bearer credential - acceptance needs no one-time code, so whoever opens it can set a password on the prefilled address and sign in as that person (verified 2026-09-21). Letting an admin type a destination would turn one mis-typed address into an account handover. Addressing it from the record means a wrong destination is a stale record, which is visible and fixable, rather than a slip nobody sees.

The URL is never returned to the client for the same reason - it goes to the sender and nowhere else.

post/api/v1/personnel/{personnel_id}/send-invite-link

Request

  • Base URL: https://api.jeevyfabrication.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.jeevyfabrication.com/api/v1/personnel/{personnel_id}/send-invite-link
  • Auth: none declared

Path parameters

personnel_idinteger required

Request body

channel'sms' required

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.