Svit.One Docs
Reference

Read an exact Person

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.

GET/v1/external/people/{personId}

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.

Authorization

projectAccessToken
AuthorizationBearer <token>

Server-to-server Project Access Token. Requests operate in the token's Project.

In: header

Path Parameters

personId*string
Length1 <= length

Response Body

application/json

curl -X GET "https://api-external.svit.one/api/v1/external/people/string"
{
  "id": "string",
  "name": "string",
  "description": "string",
  "emails": [
    "string"
  ],
  "organizationId": "string",
  "ownerUserId": 0,
  "phones": [
    "string"
  ],
  "position": "string",
  "tags": [
    "string"
  ],
  "createdAt": "string",
  "updatedAt": "string"
}
Empty
Empty

Look up a Person by an exact external identity GET

Requires the same Integration-level token allowlist as associated creation. Returns only the current active Person ID for this exact source key, not an original response replay or source observation. No identity is claimed or refreshed. Unknown, retired, archived, deleted and Organization-owned keys return the same 404.

Resolve an initial Person association candidate POST

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.