[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2023-12-13 (世界標準時間)。"],[[["All Display & Video 360 API requests must be authorized by an authenticated user using OAuth 2.0 and include an authorization token."],["Applications need to be registered with Google API Console and obtain necessary credentials, including client ID and client secret, to authorize requests."],["Users authenticating with the Display & Video 360 API need the appropriate user role (Read only, Standard, or Admin) to access and manipulate resources based on their permissions."],["The authorization process involves requesting specific scopes of access, user consent, and Google providing short-lived access tokens for data retrieval."],["Google API client libraries can simplify the authorization process and are available for various programming languages."]]],["Applications accessing private data via the Display & Video 360 API must use OAuth 2.0 for authorization, including an authorization token with each request. The process involves registering the application with the Google API Console to receive credentials. When access is requested, the user is prompted to grant consent, upon approval, a short-lived access token is provided. The user must also have a valid Display & Video 360 user role (Read only, Standard, or Admin).\n"]]
