Unlinks an agent user from Google. As a result, all data related to this user will be deleted.
Here is how the agent user is created in Google:
- When a user opens their Google Home App, they can begin linking a 3p partner.
- User is guided through the OAuth process.
- After entering the 3p credentials, Google gets the 3p OAuth token and uses it to make a devices.sync call to the 3p partner and gets back all of the user's data, including
- Google creates the agent user and stores a mapping from the
agentUserId-> Google ID mapping. Google also stores all of the user's devices under that Google ID.
The mapping from
agentUserId to Google ID is many to many, since one Google user can have multiple 3p accounts, and multiple Google users can map to one
agentUserId (e.g., a husband and wife share one Nest account username/password).
The third-party user's identity is passed in as
agentUserId. The agent is identified by the JWT signed by the partner's service account.
Note: Special characters (except "/") in
agentUserId must be URL-encoded.
The URL uses gRPC Transcoding syntax.
Required. Third-party user ID.
Request ID used for debugging.
The request body must be empty.
If successful, the response body will be empty.
Requires the following OAuth scope:
For more information, see the OAuth 2.0 Overview.