Contacts

Trigger Auto Merge

Run auto-merge once. RECORDS ARE DESTROYED.

Each merge removes one record and moves its data onto the survivor. The only way back is POST /duplicates/undo-merge/{merge_history_id}, one merge at a time. Send dry_run=true first.

A 200 does NOT by itself mean anything merged: if the org has auto-merge disabled or is in shadow mode the response says so instead of failing, which is the app's behaviour and is preserved here. Read the body.

post/duplicates/auto-merge

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/duplicates/auto-merge
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

entity_type'contact' | 'company' required

Object to merge.

dry_runboolean

Report what would merge without merging it.

Response

Successful Response

dataCrmRecordPayload required

An open envelope for one record, one dashboard or one job receipt.

Open because most of these reads are COMPUTED shapes - an engagement summary, a next-best-step, an intelligence status - that grow with the product, and dropping a field from an advisory read makes it say "nothing to report" rather than "we did not tell you".

Changes

No recorded changes to this operation across all 2 revisions of this API.