Every new line item needs to declare whether or not they will serve Eurpoean Union (EU) political ads. Display & Video 360 API and SDF uploads that don't provide declarations will fail. See our deprecations page for more details.
Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
Display & Video 360 API v1 is retired, and this documentation details the GET method for retrieving user information using the updated API.
This method requires specific authentication outlined in the Managing Users guide, and the "Try this method" feature is unavailable.
The request is made to a specific URL with the user ID as a path parameter, requiring an empty request body.
A successful response returns user details as defined in the User object documentation, and authorization requires a specific OAuth scope for user management.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[],["The core content outlines how to retrieve a user via the Display & Video 360 API, noting that version 1 is no longer available. A `GET` request to `https://displayvideo.googleapis.com/v1/users/{userId}` is required, with the `userId` specified as a path parameter. The request body should be empty. Successful requests return a `User` instance in the response body. Utilizing this method requires specific prerequisites from the Managing Users guide, and the scope `https://www.googleapis.com/auth/display-video-user-management` for authorization.\n"]]
