Merge Contacts
Merge contacts.
A contact (user) is a person in your project's membership directory, with one or more linked logins (identities). Membership manages their profile, identities, roles, and lifecycle.
Merges the contacts.
JWT Bearer Authorization
The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3
Merge contacts
CorrelationId for each request
Specify culture code when your response from the API should be localised. E.g.: en
TimeZone
The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3
Target environment for this request (e.g. TEST, STAGING). Optional — when omitted the request runs against PROD. Can be passed in a header as norbix-env.
ID of your project. Can be passed in a header as norbix-project-id.
The contact id (ct_…) that will remain after the merge (the survivor).
The contact ids (ct_…) to merge into the survivor and archive. At least one.
Success
EmptyResponse
POST /{version}/membership/users/merge HTTP/1.1
Host: hub.norbix.ai
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: multipart/form-data
Accept: */*
Content-Length: 155
{
"survivorId": "text",
"mergedIds": [
"text"
],
"projectId": "text",
"env": "text",
"cultureCode": "text",
"timeZoneId": "text",
"correlationId": "text",
"version": "text"
}Success
{
"success": {
"responseStatus": {
"isSuccess": true
}
},
"responseStatus": {
"isSuccess": true
}
}In Cloud
Manage this visually in Cloud — see Membership → Users.
Use it from code
Every Norbix SDK exposes this endpoint as a method — see Merge Contacts in the SDK reference, with examples in every language.
Last updated
Was this helpful?