[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-intercom-openapi-2026-05-29-put-conversations-id-now-returns-400-on-duplicate-custom":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},"01KSSJWJ3PRNQBNK84XYM0ZSVN","2026-05-29-put-conversations-id-now-returns-400-on-duplicate-custom","Breaking","PUT \u002Fconversations\u002F{id} now returns 400 on duplicate custom attribute names","The `PUT \u002Fconversations\u002F{id}` endpoint now returns a `400 INVALID_PARAMETER` error when the request body includes `custom_attributes` and the workspace has multiple non-archived conversation custom attributes sharing the same name. Previously, the request would silently succeed by applying the update to a non-deterministic attribute. Clients that rely on the old silent-success behaviour will now receive an error and must resolve duplicate attribute names in workspace settings before retrying.","2026-05-29T10:01:13.590Z"]