Skip to content

Tighten email_verified wording on contacts create/update/bulk #696

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adisan19 merged 2 commits into from
Oct 2, 2026
Merged

Tighten email_verified wording on contacts create/update/bulk #696

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
85d254e
Tighten email_verified wording on contacts create/update/bulk
adisan19 Oct 2, 2026
2f87f3a
Drop email_verified value list from contact request descriptions
adisan19 Oct 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Drop email_verified value list from contact request descriptions 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
  • Loading branch information
@adisan19 @claude
adisan19 and claude committed Oct 2, 2026
commit 2f87f3a037b4fb6e38ff2ebc6a2cc1aed4498879
16 changes: 0 additions & 16 deletions descriptions/0/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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:
Expand Down Expand Up @@ -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:
Expand Down Expand Up @@ -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:
Expand Down
8 changes: 0 additions & 8 deletions descriptions/2.16/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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:
Expand Down
Loading