Unlink a team member
Remove a business relationship without deleting the user account.
Overview
Unlink the member from the business and clear associated business permissions and linkage. Invite-derived plan benefits can also change. Review ongoing assignments and your administrative policy before removing access.
The user is linked to the vendor administrator. The administrator intends to remove the business relationship.
- Review active work
Check how current assignments should be handled.
- Remove the relationship
Call DELETE using the returned team-member ID.
- Refresh your roster
Remove the member from your business-facing picker.
Parameters
| Field | Requirement | Description |
|---|---|---|
team_member_idstring · path | Required | The linked 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 DELETE \
--url 'https://app.bluenotary.us/api/integrationsv2/team_members/YOUR_TEAM_MEMBER_ID' \
--header "Authorization: Bearer $BLUENOTARY_API_KEY"Response
200 · Example success Illustrative values in the current response shape.
{
"success": true,
"message": "Team member unlinked successfully"
}- This operation removes the business relationship; it does not delete the underlying user.
- Do not infer automatic cancellation or reassignment of existing sessions from the unlink response.
- Unlinking can downgrade a paid plan granted through the business invitation. Confirm the account policy before removal.
- No body or extra deletion flag is needed. Repeated deletion may return 404.
Errors & recovery
| Status | What happened | What to do |
|---|---|---|
| 404 | Linked member not found | Check whether the relationship was already removed. |
| 401 | Authentication failed | Use the owning account’s 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.