关于Gmail保密模式的API变更、搜索排除及文档同步的技术问询

Let me break down your questions based on real-world testing and existing API behavior:

1. Are there API changes related to Gmail's Confidential Mode? #

As of now, Google hasn't published formal API change announcements specifically for Confidential Mode. That said, the feature does introduce subtle behavior changes in how the Gmail API interacts with confidential messages—changes that aren't always clearly spelled out in official docs.

2. Are confidential messages/threads automatically excluded from API search results? #

Yes, by default, confidential messages and threads are not returned in standard API search or list requests. To retrieve them, you need to explicitly add the is:confidential filter to your API query parameters (e.g., in the q field of users.messages.list or users.messages.search calls).

3. Do we need to modify code to avoid app failures? #

It depends on your app's use case:

• If your app needs to process all incoming messages (including confidential ones), you must update your code to include the is:confidential filter when fetching messages. Otherwise, you'll miss these threads entirely, which could lead to unexpected gaps in functionality.
• If your app doesn't handle confidential messages, your existing code might not fail outright—but you should be aware that any confidential messages sent to your users won't be visible to your app, which could cause confusion if users expect those messages to be processed.

Feedback on API Documentation #

I completely agree with your frustration here. When Gmail rolls out new features like Confidential Mode or the gmailified inbox, it's critical that the API release notes and documentation are updated in parallel to clarify how these features impact existing API workflows. Having to rely on manual testing (like you did for the gmailified inbox) adds unnecessary development time and uncertainty for developers. This is definitely an area where Google could improve transparency.

内容的提问来源于stack exchange，提问作者Alex3917