Intercom API (unofficial showcase)
GET/contacts/{id}/merge_history

Get contact merge history

Lists the contacts merged into a given contact, with results returned in pages. Use cursor to continue from a previous response and per_page and order to control the results. Merge history is available only for contacts with the user role.

5 parameters
idstringrequired
The identifier of the contact whose merge history to retrieve; the contact must have the `user` role.
cursorstringoptional
Pagination cursor from a previous response's `next_cursor` value. Omit it to retrieve the first page.
per_pageintegeroptional
Number of merge history entries per page. Must be between 1 and 150. Defaults to 50 when omitted.
Default:50
orderstringoptional
Order of results: `asc` or `desc`. Defaults to descending when omitted.
Allowed:ascdesc
Intercom-Versionstringoptional
The Intercom API version to use. Defaults to 2.17 when omitted.
Allowed:1.01.11.21.31.42.02.12.22.32.42.52.6Default:2.17

3 status codes
200Returns a paginated list of merge history entries with source contact identifiers, merge timestamps, and pagination metadata including `next_cursor` and `has_more`.
typestringoptional
The type of object.
Allowed:list
dataarray<MergeHistoryItem>optional
An array of merge history entries.
next_cursorstringoptional
A cursor to pass as the `cursor` query parameter to fetch the next page of results. Absent when there are no more pages.
has_morebooleanoptional
Whether there are more results to fetch.
401Returned when the request is unauthorized.

One documented failure

  • unauthorized

    Access Token Invalid

typestringrequired
The type is error.list
request_idstringoptional
errorsarray<object>required
An array of one or more error objects
404Returned when the contact is not found or has the `lead` role.

One documented failure

  • not_found

    Contact not found

typestringrequired
The type is error.list
request_idstringoptional
errorsarray<object>required
An array of one or more error objects

Error handling

A 401 is returned when the request is unauthorized. A 404 is returned when the id path parameter does not identify a contact or identifies a contact with the lead role; this operation is available only for contacts with the user role.