AI-generated Key Takeaways
-
Display & Video 360 API v3 has sunset, and users should use v4 instead.
-
This page describes how to update an existing user via a PATCH request to the Display & Video API v3, but this method has unique authentication requirements and the "Try this method" feature does not work.
-
The update request requires specifying the user ID in the path, an update mask as a query parameter to control which fields are updated, and a request body containing the updated user instance.
-
A successful update returns the updated user in the response body and requires the
https://www.googleapis.com/auth/display-video-user-management
authorization scope.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Updates an existing user. Returns the updated user if successful.
This method has unique authentication requirements. Read the prerequisites in our Managing Users guide before using this method.
The "Try this method" feature does not work for this method.
HTTP request
PATCH https://displayvideo.googleapis.com/v3/users/{user.userId}
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
user.userId |
Output only. The unique ID of the user. Assigned by the system. |
Query parameters
Parameters | |
---|---|
updateMask |
Required. The mask to control which fields to update. This is a comma-separated list of fully qualified names of fields. Example: |
Request body
The request body contains an instance of User
.
Response body
If successful, the response body contains an instance of User
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video-user-management
For more information, see the OAuth 2.0 Overview.