[[["易于理解","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"]],["最后更新时间 (UTC):2024-12-20。"],[[["This guide explains how third-party providers can use OAuth 2.0 to request access to their clients' merchant accounts through their apps."],["Apps accessing the Merchant API need to be verified to avoid limitations, a process that usually takes 3-5 business days."],["Incremental authorization is recommended during setup to prevent scope selection issues and ensure the app receives necessary permissions."],["All Merchant API requests must be authorized using OAuth 2.0 with a valid access token, obtainable through the described authorization flow."],["Developers can find resources such as OAuth 2.0 scope information and authorization samples within the guide for implementation."]]],["Third-party providers use OAuth 2.0 to access clients' merchant accounts, requiring app verification via Google Cloud (3-5 days). Apps must request the `https://www.googleapis.com/auth/content` scope on the consent screen, which users must manually select. Each Merchant API request needs an authorization token. The OAuth process involves registering the app, requesting a scope, user consent via a screen, receiving an access token, and attaching it to data requests.\n"]]