Reassign Contact
Use this endpoint when a contact needs to move from one captive agent to another captive agent within your agency – for example, when an agency owner reassigns a contact in your CRM and the new agent needs to quote and enroll that contact on HealthSherpa Medicare.
On HealthSherpa Medicare, a contact belongs to a single assigned agent, and only that agent can access it via the API. So if one agent created or updated a contact via the API and another agent now needs to work it, reassign the contact to them first.
Reassignment is one-way: Once a contact is reassigned, the previous agent loses access to it via the API. They also lose access to it in the HealthSherpa Medicare platform – unless they have Admin or Full Book access. Consider surfacing this to the agent for awareness or confirmation before making the call – example.
Terminology note: when we say captive agent, that includes Full Book and Admin users.
Reassigns a contact to another agent so the new agent may quote and enroll the contact on HealthSherpa Medicare. Two callers can do this: the agent who currently owns the contact, or an agency admin who has the contact reassignment permission on the agency that owns the contact's book. Name the receiving agent by email. The current owner and the receiving agent must both be captive in the agency that owns the contact's book. If the caller is the current owner, this is a one-way door: once the contact is reassigned, this access token can no longer access the contact via the API or in the platform.
- : Access to Partner API v2 endpoints
OAuth 2.0 authentication with partner_api_v2 scope
The HealthSherpa system ID of the contact to reassign
Email address of the agent who should receive the contact
Contact reassigned successfully. The contact object has the same shape the update endpoint returns, and redirect_url is regenerated for the receiving agent.
The agent_email field is missing or is not a valid email address
Unauthorized - Invalid, missing, or expired OAuth access token. 401 responses for token problems are produced by the OAuth layer and follow the OAuth 2.0 Bearer Token error format ({"error": "...", "error_description": "..."}) rather than the standard {error: {code, message}} envelope used by the rest of the API.
The access token does not have the required partner_api_v2 scope. Like other OAuth errors, this response uses the OAuth 2.0 Bearer Token error format.
Either the contact does not exist or the authenticated agent cannot reassign it (resource_not_found), or no captive agent in the contact's agency has the supplied agent_email (agent_not_found).
The request was well-formed but the reassignment is not allowed, either because of the agents involved or because the receiving agent already has a contact with this external_id.
POST /v2/contacts/{contact_id}/reassign HTTP/1.1
Host: api.medicare.healthsherpa.com
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 39
{
"agent_email": "new.agent@example.com"
}{
"data": {
"contact": {
"id": "c7716192-7625-4351-a689-3df3b65ba0e2",
"slug": "jane-testbasic",
"external_id": "TEST-1738780800000-abc123",
"first_name": "Jane",
"last_name": "TestBasic",
"type": "client"
},
"redirect_url": "https://medicare.healthsherpa.com/agents/new-agent-name/plans/c7716192-7625-4351-a689-3df3b65ba0e2"
}
}Last updated