Regenerate an onboarding link
Generate a fresh access link for a linked team member.
Overview
Generate a fresh onboarding link for a linked team member. Although the route is named resend_invite, your application is responsible for delivering the returned link; this operation does not send the invitation email.
The member must be linked to the vendor administrator. Choose a private delivery channel for the returned access link.
- Verify the member
Confirm the intended user and business relationship.
- Generate a fresh link
Call resend_invite without a body.
- Deliver privately
Send the returned link through your selected channel.
Parameters
| Field | Requirement | Description |
|---|---|---|
team_member_idstring · path | Required | The BlueNotary user ID. No request body is required. |
Request example
Use a server-side API key. Replace example IDs and values before using this request in an approved test environment.
curl --request POST \
--url 'https://app.bluenotary.us/api/integrationsv2/team_members/YOUR_TEAM_MEMBER_ID/resend_invite' \
--header "Authorization: Bearer $BLUENOTARY_API_KEY"Response
200 · Example success Illustrative values in the current response shape.
{
"success": true,
"onboarding_link": "https://app.bluenotary.us/sign-in?REDACTED_ONBOARDING_TOKEN"
}- Regeneration rotates the session password, invalidating previously issued links that depend on it.
- Treat onboarding_link as a credential and avoid storing it in analytics or routine logs.
- The login-link endpoint’s 12-hour expiry must not be assumed to apply to onboarding links.
- Repeated calls can invalidate a link you already sent. Generate once and deliver the newest link.
Errors & recovery
| Status | What happened | What to do |
|---|---|---|
| 404 | Member or relationship not found | Confirm the user is linked to this vendor account. |
| 403 | Vendor admin user not found | Confirm the owning business administrator account is active. |
| 422 | Invalid member identifier | Use the valid BlueNotary user ID returned by a team-member operation. |
| 401 | Authentication failed | Use a valid API key. |
Explore the response
Response simulator
LOCAL EXAMPLEExplore the example response without an API key. This does not send requests or validate your account configuration.
This example uses the resource ID shown in the endpoint path.