# Verato Person API

Version: 2026.1.2

## Servers

Production Link API
```
https://yourveratodomain.com/link-ws/svc
```

Sandbox Link API
```
https://yourveratodomain.com/link-ws/svc
```

## Security

### basicAuth

Type: http
Scheme: basic

## Download OpenAPI description

 - [Verato Person API](https://developer.verato.com/_bundle/apis/person.openapi.yaml)

 - [POST /v2/postIdentity](https://developer.verato.com/apis/person.openapi/other/post_v2_postidentity.md): Adds or updates an identity record in the Person entity — the Source + Native ID in the request determines whether the call creates a new identity or updates an existing one, and every response return
 - [POST /v2/demographicsSearch](https://developer.verato.com/apis/person.openapi/other/post_v2_demographicssearch.md): Performs a fuzzy search across the Person entity for identities that are potential matches to a set of demographic attributes, returning one-to-many ranked results with match scores rather than a sing
 - [POST /v2/demographicsQuery](https://developer.verato.com/apis/person.openapi/other/post_v2_demographicsquery.md): Retrieves the single best-matching identity in the Person entity for a set of demographic attributes, returning a match only if it scores at or above the same threshold used during postIdentity matchi
 - [POST /v2/identityIdQuery](https://developer.verato.com/apis/person.openapi/other/post_v2_identityidquery.md): Queries the Person entity for an identity using its Verato Link ID. This is the primary way to retrieve an identity when you already have the Link ID from a previous operation.
 - [POST /v2/nativeIdQuery](https://developer.verato.com/apis/person.openapi/other/post_v2_nativeidquery.md): Retrieves the single identity in the Person entity that contains the given Source + Native ID. Use this when you have a source system's own record identifier and need to look up the corresponding Vera
 - [POST /createDataSource](https://developer.verato.com/apis/person.openapi/other/post_createdatasource.md): Creates one or more new data sources in the Universal Identity platform. Up to 10 data sources can be created per call. Newly added sources may take 10–15 minutes to become available. This service onl
 - [POST /deleteSourceIdentity](https://developer.verato.com/apis/person.openapi/other/post_deletesourceidentity.md): Physically deletes a source record from the Person entity to keep Verato in sync when a record is deleted from a source system. If it's the only source record in an identity, the whole identity is del
 - [POST /reactivateSourceWs](https://developer.verato.com/apis/person.openapi/other/post_reactivatesourcews.md): Reactivates a source record in the Person entity that was previously deactivated, restoring it to its original Link ID. Use this to reverse a deactivateSourceWs call.
 - [POST /deactivateSourceWs](https://developer.verato.com/apis/person.openapi/other/post_deactivatesourcews.md): Logically deletes (deactivates) a source record in the Person entity so it's excluded from future matching while remaining visible in the UI and API responses. Deactivated records can later be restore
 - [POST /householdQuery](https://developer.verato.com/apis/person.openapi/other/post_householdquery.md): Retrieves the set of Link IDs grouped into a household, looked up by Link ID, Source + Native ID, or Household ID. Households group multiple Person entities based on shared core or extended attributes
 - [POST /linkIdentities](https://developer.verato.com/apis/person.openapi/other/post_linkidentities.md): Forces two identity records (by Source + Native ID) into the same Link ID even though their demographic data wasn't similar enough to match automatically. Use this on an exception basis when you have
 - [POST /mergeIdentities](https://developer.verato.com/apis/person.openapi/other/post_mergeidentities.md): Merges a "toRetire" source record into a "toSurvive" source record, forcing them into the same Link ID and marking the retired source as merged/inactive. After a merge, the retired source's attribute
 - [POST /searchNotifications](https://developer.verato.com/apis/person.openapi/other/post_searchnotifications.md): Retrieves a paginated feed of notification messages describing identity-changing events (matches, links, merges, deactivations, overlays, etc.) that occurred in the Person entity within a specified da
 - [POST /unlinkIdentities](https://developer.verato.com/apis/person.openapi/other/post_unlinkidentities.md): Forces apart two identity records that had been matched or linked into the same Link ID, splitting one out into its own new Link ID. Use this to reverse a linkIdentities call or to split records that
 - [POST /unmergeIdentities](https://developer.verato.com/apis/person.openapi/other/post_unmergeidentities.md): Reactivates a previously merged/retired source record and splits it out of its current Link ID into a new one of its own. Use this only to reverse a mergeIdentities call made in error.
 - [POST /addRelationshipService](https://developer.verato.com/apis/person.openapi/other/post_addrelationshipservice.md): Creates a direct relationship (e.g., "is parent of") between two Person entities, identified by their Link IDs, with optional start and end dates and a status. Use this to model family or guardianship
 - [POST /searchRelationshipsService](https://developer.verato.com/apis/person.openapi/other/post_searchrelationshipsservice.md): Searches for existing relationships between Person entities, filterable by subject Link ID, object Link ID, or relationship verb. Use this to look up how a given identity is connected to others (e.g.,
 - [POST /deleteRelationshipService](https://developer.verato.com/apis/person.openapi/other/post_deleterelationshipservice.md): Deletes an existing relationship between two Person entities that was previously created with addRelationshipService. There is no legacy Patient Journey equivalent — this endpoint is new to the platfo