Skip to content

Document email_verified on the bulk contact request items #694

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
dan0505 merged 1 commit into from
Oct 1, 2026
Merged

Document email_verified on the bulk contact request items #694

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 12 additions & 0 deletions descriptions/0/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31003,6 +31003,12 @@ components:
type: string
description: The contact's email address.
example: joe@example.com
email_verified:
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.
example: true
name:
type: string
description: The contact's name.
Expand Down Expand Up @@ -31146,6 +31152,12 @@ components:
type: string
description: The contact's email address.
example: joe@example.com
email_verified:
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.
example: true
name:
type: string
description: The contact's name.
Expand Down
Loading