[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-intercom-openapi-2026-07-09-merge-contacts-request-fields-from-and-into-are-now-required":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"intercom-openapi","Intercom REST API","intercom","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fintercom\u002FIntercom-OpenAPI\u002Fmain\u002Fdescriptions\u002F2.15\u002Fapi.intercom.io.yaml",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KX38K7GFV2VZFA6669THTDN2","2026-07-09-merge-contacts-request-fields-from-and-into-are-now-required","Breaking","merge_contacts_request fields 'from' and 'into' are now required","The `merge_contacts_request` schema now marks **`from`** and **`into`** as `required` fields. Clients that previously omitted either field (relying on them being optional) will now fail schema validation. This affects any integration that merges contacts without explicitly providing both identifiers.","2026-07-09T11:00:51.855Z"]