Sending Invitations to Identities for Self-Registration to Applications Using SailPoint IdentityNow

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hello Team,

We are exploring a use case where we would like to send invitations to identities so they can register themselves for an application through SailPoint IdentityNow.

Could you please clarify:

  • Whether IdentityNow supports sending invitations (email or notification) to identities for self-registration or onboarding to an application?

  • If yes, what API endpoints or configuration steps are available to implement this functionality?

  • Any recommended best practices or prerequisites for enabling this capability?

We appreciate any documentation or examples you can share to guide us on implementing this.

Thanks in advance,
Isha

2

Hi @IshaSingh ,

Main Recommendation:
SailPoint IdentityNow (ISC) does support sending invitation emails for users to self-register or onboard to applications via both the UI and a public REST API. To implement:

  1. Configure your identity profiles’ invitation settings in the Admin UI.

  2. Call the POST /identities/invite endpoint to programmatically send invitations.

  3. Monitor the task status and adhere to invitation prerequisites.

1. Invitation Options in the Admin UI

IdentityNow provides manual and automatic invitation capabilities without any custom code:

  • Manual Invites:

    • Go to Admin > Identity Management > Identities.

    • Select one or multiple identities and choose Actions > Invite Identity(ies) to email them a registration link.

  • Automatic Invites:

    • Under Admin > Identity Management > Identity Profiles, edit a profile’s Invitation Options to:

    • Send invites upon identity creation.

    • Send invites when identities enter a specified lifecycle state.

Invitations expire after 7 days. Expired invites can be automatically resent for auto-invite profiles or resent manually for manual invites. sailpoint

2. Programmatic Invitations via API

For automation and integration workflows, use the Invite Identities API:

Endpoint

POST https://{tenant}.api.identitynow.com/identities/invite Authorization: Bearer {access_token} Content-Type: application/json

Request Body

{   "identityIds": ["1797782","1675056"] }

  • identityIds: Array of internal IdentityNow IDs for the unregistered identities you wish to invite.

  • Only unregistered identities receive invites; registered or pending identities are ignored.

Response

  • 202 Accepted: Returns a taskId to track progress.

  • Use GET /tasks/{taskId} via Task Management API to poll status.

Prerequisites:

  • Each identity must have a unique, valid work email in your authoritative source.

  • Identities must already exist in IdentityNow and be in an unregistered state.

This endpoint is officially documented in the SailPoint Developer site under Invite identities to register. developer.sailpoint

3. Best Practices & Prerequisites

  1. Email Uniqueness: Ensure each identity has a unique primary email—IdentityNow only sends to the first matching identity per address.

  2. Invitation Templates: Customize your registration email template under Admin > Email Templates. Prefix the Subject with #stop or no_send to suppress automated sends when testing.

  3. Monitoring & Retries:

    • Invitations queue in 1,000-message batches every 30 minutes for automatic profiles.

    • Use Task Management to detect failures (e.g., invalid email address) and implement retry logic.

  4. Expiration Handling: Invitations auto-expire after 7 days. For manual invites, detect expiration and call the API again to resend.

References for Implementation: