From 85d254e6fa4ab43ee2aa2a98f6da1ce0240f7412 Mon Sep 17 00:00:00 2001 From: adisa narula Date: Fri, 2 Oct 2026 14:41:24 +0100 Subject: [PATCH 1/2] Tighten email_verified wording on contacts create/update/bulk Co-Authored-By: Claude Opus 5.5 --- descriptions/0/api.intercom.io.yaml | 36 +++++++++++++++++--------- descriptions/2.16/api.intercom.io.yaml | 20 +++++++------- 2 files changed, 34 insertions(+), 22 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 31852498..6ba2e883 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -31022,7 +31022,13 @@ components: type: boolean nullable: true description: |- - Whether the contact has proved they own this email address: `true` records that proof, `false` marks the address unverified, and omitting it leaves the current status unchanged. Send it in the same contact object as `email`; a contact object that includes `email_verified` without `email` is rejected. Behaves exactly like `email_verified` on [Create a contact](/docs/references/preview/rest-api/api.intercom.io/contacts/createcontact), which describes the field in full. + Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. + + - `true`: verified. Only send `true` when you have this proof. + - `false`: not verified. + - Omitted: new contacts are not verified; existing contacts keep their current value. + + Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true name: type: string @@ -31171,7 +31177,13 @@ components: type: boolean nullable: true description: |- - Whether the contact has proved they own this email address: `true` records that proof, `false` marks the address unverified, and omitting it leaves the current status unchanged. Send it in the same contact object as `email`; a contact object that includes `email_verified` without `email` is rejected. Behaves exactly like `email_verified` on [Update a contact](/docs/references/preview/rest-api/api.intercom.io/contacts/updatecontact), which describes the field in full. + Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. + + - `true`: verified. Only send `true` when you have this proof. + - `false`: not verified. + - Omitted: new contacts are not verified; existing contacts keep their current value. + + Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true name: type: string @@ -34960,13 +34972,13 @@ components: type: boolean nullable: true description: |- - Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`. + Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: ownership is proved. - - `false`: ownership is not proved. - - Omitted: the current verification status stays the same. + - `true`: verified. Only send `true` when you have this proof. + - `false`: not verified. + - Omitted: new contacts are not verified; existing contacts keep their current value. - New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one. + Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true phone: type: string @@ -43361,13 +43373,13 @@ components: type: boolean nullable: true description: |- - Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`. + Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: ownership is proved. - - `false`: ownership is not proved. - - Omitted: the current verification status stays the same. + - `true`: verified. Only send `true` when you have this proof. + - `false`: not verified. + - Omitted: new contacts are not verified; existing contacts keep their current value. - New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one. + Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true phone: type: string diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index e6ac01cb..6f6cdd9f 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -28848,13 +28848,13 @@ components: type: boolean nullable: true description: |- - Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`. + Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: ownership is proved. - - `false`: ownership is not proved. - - Omitted: the current verification status stays the same. + - `true`: verified. Only send `true` when you have this proof. + - `false`: not verified. + - Omitted: new contacts are not verified; existing contacts keep their current value. - New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one. + Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true email: type: string @@ -35667,13 +35667,13 @@ components: type: boolean nullable: true description: |- - Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`. + Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: ownership is proved. - - `false`: ownership is not proved. - - Omitted: the current verification status stays the same. + - `true`: verified. Only send `true` when you have this proof. + - `false`: not verified. + - Omitted: new contacts are not verified; existing contacts keep their current value. - New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one. + Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true phone: type: string From 2f87f3a037b4fb6e38ff2ebc6a2cc1aed4498879 Mon Sep 17 00:00:00 2001 From: adisa narula Date: Fri, 2 Oct 2026 15:00:50 +0100 Subject: [PATCH 2/2] Drop email_verified value list from contact request descriptions Co-Authored-By: Claude Opus 5.5 --- descriptions/0/api.intercom.io.yaml | 16 ---------------- descriptions/2.16/api.intercom.io.yaml | 8 -------- 2 files changed, 24 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 6ba2e883..fc42e8b3 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -31024,10 +31024,6 @@ components: description: |- Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: verified. Only send `true` when you have this proof. - - `false`: not verified. - - Omitted: new contacts are not verified; existing contacts keep their current value. - Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true name: @@ -31179,10 +31175,6 @@ components: description: |- Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: verified. Only send `true` when you have this proof. - - `false`: not verified. - - Omitted: new contacts are not verified; existing contacts keep their current value. - Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true name: @@ -34974,10 +34966,6 @@ components: description: |- Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: verified. Only send `true` when you have this proof. - - `false`: not verified. - - Omitted: new contacts are not verified; existing contacts keep their current value. - Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true phone: @@ -43375,10 +43363,6 @@ components: description: |- Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: verified. Only send `true` when you have this proof. - - `false`: not verified. - - Omitted: new contacts are not verified; existing contacts keep their current value. - Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true phone: diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index 6f6cdd9f..a1d92249 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -28850,10 +28850,6 @@ components: description: |- Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: verified. Only send `true` when you have this proof. - - `false`: not verified. - - Omitted: new contacts are not verified; existing contacts keep their current value. - Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true email: @@ -35669,10 +35665,6 @@ components: description: |- Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected. - - `true`: verified. Only send `true` when you have this proof. - - `false`: not verified. - - Omitted: new contacts are not verified; existing contacts keep their current value. - Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address. example: true phone: