Resolve an initial Person association candidate
Read-only search under properties.personAssociation.projectAccessTokenIds and its explicit svit-user onboardingPolicy. The source's exact IDs must be canonical Svit User IDs. Existing exact associations win; otherwise preserved cutover evidence precedes unique lowercase/trim email matching. Conflicting history never falls back to email. Results are hints, not reservations; linking repeats the policy transactionally. No profiles or historical values are returned. POST keeps email out of URLs.
/v1/external/people/association-candidates/searchRead-only search under properties.personAssociation.projectAccessTokenIds and its explicit svit-user onboardingPolicy. The source's exact IDs must be canonical Svit User IDs. Existing exact associations win; otherwise preserved cutover evidence precedes unique lowercase/trim email matching. Conflicting history never falls back to email. Results are hints, not reservations; linking repeats the policy transactionally. No profiles or historical values are returned. POST keeps email out of URLs.
Authorization
projectAccessToken Server-to-server Project Access Token. Requests operate in the token's Project.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://api-external.svit.one/api/v1/external/people/association-candidates/search" \ -H "Content-Type: application/json" \ -d '{ "integrationId": "497a18ca-284e-40c0-985d-f72be35d468e", "externalId": "string", "email": "string" }'{
"status": "candidate",
"personId": "string",
"matchedBy": "historical"
}Read an exact Person GET
Reads a Person only within the server token's Project. Archived People remain readable; deleted, missing, foreign-Project and Organization identifiers return non-disclosing 404s.
Submit external form POST
Submit a contact form from an external website. Creates a new person record in the CRM system. Requires a valid client token in the x-client-token header.