Merge duplicate custom fields
Merge a duplicate custom field into a canonical field without overwriting data. Source values copy only into empty targets; identical duplicates and blank source values are removed. Different non-empty values remain on the source and prevent it from being archived. Both fields must be active and have the same type.
Authorizations
Org-scoped Norbelys API key. Create one in Settings → API keys and send it as Authorization: Bearer ak_….
Headers
Opt-in idempotency for a safely retried write: reuse the same key to replay the original result for 24h instead of re-executing. Recommended on every POST.
255Path Parameters
The duplicate/source field id whose values should be migrated.
"fld_legacy_company"
Body
The canonical destination field id.
"fld_canonical_company"
Response
OK
Contacts whose identical source value was removed because the target already contained it.
x >= 0Contacts with two different non-empty values. Both values were preserved and the source field remains active.
x >= 0Contacts that had the source key when the merge began.
x >= 0Contacts whose source value was copied into an empty target and then removed from the source key.
x >= 0Whether source and target define different non-null defaults. A conflict keeps the source field active.
Contacts whose source key was removed because its value was null or blank.
x >= 0The source field after the merge.
Whether the source was archived. This is true only when no source values or default conflict remain.
Contacts that still carry the source key, normally because its value conflicts with the target.
x >= 0The canonical target field after the merge.
Always "field_merge" — the resource discriminator.