# New identity fields in OAuth token responses

By Steven Van · 2026-07-15

User objects now include an email\_verified boolean next to person.email, indicating whether Notion has verified that email address.

[Notion](<https://creatorstoolbox.com/tools/notion>)'s API now reports whether a user's email address has been verified, and OAuth clients built on Notion MCP can identify who authorized a connection without a follow-up call.

- User objects gain an **email\_verified** boolean next to person.email. It shows up anywhere a person's email appears, including the owner field in OAuth token responses and in List all users results.

- Notion MCP token responses now include top-level **user\_id**, **workspace\_id**, and **email\_domain** fields on successful authorization-code exchanges, so MCP clients can tie a connection to a Notion user and workspace without an extra request. See [Integrating your own MCP client](<https://developers.notion.com/page/changelog#july-15-2026>).

Both fields are backwards-compatible additions that appear on every API version. Notion recommends parsing responses leniently and ignoring fields a client doesn't recognize.

[![](<https://notion-demo.mintlify.app/images/og-image.png>)](<https://developers.notion.com/page/changelog#july-15-2026>)

![Notion](<https://www.google.com/s2/favicons?domain=notion.so&sz=128>)

Notion

All-in-one workspace for notes, docs, projects, and wikis — with AI built in for writing, summarizing, and organizing.

[View Notion →](<https://creatorstoolbox.com/tools/notion>)

Sources

[Original source](<https://developers.notion.com/page/changelog#july-15-2026>)

[Read New identity fields in OAuth token responses on Creators Toolbox](<https://creatorstoolbox.com/blog/notion-new-identity-fields-in-oauth-token-responses>)

---
Canonical source: https://creatorstoolbox.com/blog/notion-new-identity-fields-in-oauth-token-responses