curl --request POST \
--url https://go.aiinsurance.io/api/v1/companies/{companyId}/entities/{entityType}/{entityId}/email-people/{personId}/link-earlier \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"from": "2026-01-10T00:00:00Z",
"cause": "person_added"
}
'{
"queued": true
}Link Earlier Record Emails
Links a person’s email on a record from an earlier date. A person’s email
links to a record from the day they were added to it; this moves that
date earlier and links their older email in the background. from: null
links all of it. Call it after adding a contact or attorney to bring in
their earlier email, as the app’s “Link their emails from what date?”
does.
The date only moves earlier: a later from returns 400. Sending the
same date again finishes linking that an earlier call left. A link
someone removed stays removed.
The person must be on the record with an email address. Answers 404
while email is not turned on for the company.
Required permission: <resource>.edit for the path’s {entityType}
(event.edit, exposure.edit, quote.edit, submission.edit,
person.edit, organization.edit), and <resource>.view.
curl --request POST \
--url https://go.aiinsurance.io/api/v1/companies/{companyId}/entities/{entityType}/{entityId}/email-people/{personId}/link-earlier \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"from": "2026-01-10T00:00:00Z",
"cause": "person_added"
}
'{
"queued": true
}Authorizations
User-principal OAuth 2.0 Bearer authentication. Send a user-scoped Auth0 access token (audience = the app API audience) as Authorization: Bearer <jwt>. The request resolves to the user's identity and is authorized by their Role on the {companyId} in the path — the same role-based permissions the web app enforces. This is the path the MCP connector uses to act on a user's behalf; endpoints that accept it list both BearerAuth and ApiKeyAuth.
Path Parameters
Field Model V1 entity type (lowercase kebab-case URL slug). One of the six
CRUD entity types: event, exposure, quote, submission, person,
organization. policy is NOT valid here — Policy has no generic CRUD (its
writes go through the policy transaction endpoints), though it does have a
read-only /configuration schema.
event, exposure, quote, submission, person, organization