OPTIONS - 

The OPTIONS method supplies information about the viability of this merge, using the Allow HTTP header. If this merge is viable, the Allow will indicate that both GET, POST may be applied. If the merge is available when the roles of the survivor and non-survivor are switched, a Link header will be supplied linking to the "merge mirror." When the merge is NOT viable, the Allow header will NOT include a GET or POST. The Warning header will contain details as to the reason the merge is not viable.

Name	Type	Description
dpid	path	The id of the duplicate.
pid	path	The id of the survivor.

• 200  -  Upon a successful read.

450	Unable to merge. Warning message will contain the details.

GET - 

Read the current state of the potential merge by performing a merge analysis. The filter request parameter may be specified indicating which categories of information need to be analyzed. If no filter is specified then all categories will be used. The valid filter categories are listed below.

Filter	Description
CoupleRelationships	Analyze couple relationships
NonVitalConclusions	Analyze non-vital conclusions
ParentChildRelationshipsAsChild	Analyze parent-child relationships as child
ParentChildRelationshipsAsParent	Analyze parent child relationships as parent
SourceReferences	Analyze source references
VitalConclusions	Analyze vital conclusions

The following results will be returned in the merge analysis.

Category	Description
survivorResources	A list of resources that are unique to the survivor person or have same value in both survivor and duplicate persons
duplicateResources	A list of resources on the duplicate person that do not exist on the survivor person
conflictingResources	A list of conflicts where the resource exists in the survivor and the duplicate persons and have different values
survivor	A person resource retained in the merge process
duplicate	The person resource deleted in the merge process

Name	Type	Description
dpid	path	The id of the duplicate.
pid	path	The id of the survivor.
filter	query	The filter to apply to the merge analysis. One of "CoupleRelationships", "NonVitalConclusions", "ParentChildRelationshipsAsChild", "ParentChildRelationshipsAsParent", "SourceReferences", "VitalConclusions".

• 200  -  Upon a successful read.
• 204  -  Upon a successful query with no results.
• 301  -  If the person has been merged into another person.
• 404  -  If the person is not found.
• 410  -  If the person has been deleted.
• 429  -  If the request was throttled.

POST - This method performs a person merge as specified by a Person ID (survivor) and Duplicate Person ID along with the list of resources to be merged. All resources from the survivor person that need to be deleted must be specified. All resources that should be copied from the duplicate person to the survivor must be specified. If a resource is copied and a resource of the same type already exists on the survivor then that resource must be deleted from the survivor.

Name	Type	Description
X-Reason	header	The reason for the merge.
dpid	path	The id of the duplicate.
pid	path	The id of the survivor.
body	request-body	- Object containing a list of resources to merge

• 204  -  The update was successful.
• 404  -  If the requested resource is not found.
• 429  -  If the request was throttled.