對要求進行授權
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
所有向 Google Street View Publish API 發出的要求都必須經過驗證。上傳新圖像時，系統會將圖像歸給已驗證使用者的 Google 帳戶。
您的應用程式傳送至 Google Street View Publish API 的每項要求，都必須包含授權權杖。這個權杖也可讓 Google 識別您的應用程式。
關於授權通訊協定
您的應用程式必須使用 OAuth 2.0 對要求進行授權，系統不支援其他授權通訊協定。如果您的應用程式採用使用 Google 帳戶登入功能，系統會為您處理部分授權事項。
使用 OAuth 2.0 對要求進行授權
凡是傳送至 Google Street View Publish API 的要求，都必須由已驗證的使用者授權。
OAuth 2.0 授權程序 (或「流程」) 的細節會根據您編寫的應用程式類型而有所不同。下列一般程序適用於所有應用程式類型：
- 建立應用程式後，請透過 Google API 控制台註冊應用程式。接著 Google 會向您提供稍後需要的資訊，例如用戶端 ID 和用戶端密碼。
- 在 Google API 控制台中啟用 Google 街景發布 API。(如果 API 控制台裡沒有列出該 API，則可略過這個步驟)。
- 當應用程式需要存取使用者資料時，會向 Google 要求特定的存取範圍。
- Google 會向使用者顯示同意畫面，請對方授權您的應用程式要求部分資料。
- 如果使用者同意，Google 即會授予短期存取權杖給您的應用程式。
- 您的應用程式向使用者要求資料，並且在要求中附上存取權杖。
- 如果 Google 判定您的要求與權杖有效，便會傳回您要求的資料。
部分流程包含額外步驟，例如使用「更新權杖」來取得新的存取權杖。如要進一步瞭解各類應用程式的流程，請參閱 Google 的 OAuth 2.0 說明文件。
以下是 Google Street View Publish API 的 OAuth 2.0 範圍資訊：
| 範圍 |
意義 |
https://www.googleapis.com/auth/streetviewpublish |
讀取/寫入權限。 |
如要透過 OAuth 2.0 要求存取權，您的應用程式需要範圍資訊，以及 Google 在您註冊應用程式時提供的資訊 (例如用戶端 ID 和用戶端密碼)。
提示：Google API 用戶端程式庫可以為您處理部分授權程序，且適用於多種程式設計語言；詳情請參閱程式庫和範例頁面。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-29 (世界標準時間)。
[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[[["\u003cp\u003eAll requests to the Google Street View Publish API require authentication using the Google account of the user uploading imagery.\u003c/p\u003e\n"],["\u003cp\u003eApplications must utilize OAuth 2.0 for authorization, obtaining an access token through a consent screen where users grant access.\u003c/p\u003e\n"],["\u003cp\u003eWhen registering your application with Google API Console, you receive a client ID and client secret, which, alongside the necessary scope information, are used during the authorization process.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Street View Publish API offers read/write access through the scope \u003ccode\u003ehttps://www.googleapis.com/auth/streetviewpublish\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's client libraries, available for various programming languages, can simplify parts of the authorization process.\u003c/p\u003e\n"]]],["Requests to the Google Street View Publish API require OAuth 2.0 authorization, using an access token. User applications must be registered via the Google API Console to obtain a client ID and secret. When access to user data is required, a specific scope must be requested. The user is presented with a consent screen. Upon approval, an access token is provided, which the application uses to request data. The API supports read/write access via the `https://www.googleapis.com/auth/streetviewpublish` scope.\n"],null,["# Authorize Requests\n\nAll requests to the Google Street View Publish API must be authenticated. When new imagery is uploaded, it will be attributed to the Google account of the authenticated user.\n\nEvery request your application sends to the Google Street View Publish API must include an authorization token. The token also identifies your application to Google.\n\nAbout authorization protocols\n-----------------------------\n\nYour application must use [OAuth 2.0](https://developers.google.com/identity/protocols/OAuth2) to authorize requests. No other authorization protocols are supported. If your application uses [Sign In With Google](https://developers.google.com/identity/gsi/web), some aspects of authorization are handled for you.\n\nAuthorizing requests with OAuth 2.0\n-----------------------------------\n\nAll requests to the Google Street View Publish API must be authorized by an authenticated user.\n\nThe details of the authorization process, or \"flow,\" for OAuth 2.0 vary somewhat depending on what kind of application you're writing. The following general process applies to all application types:\n\n1. When you create your application, you register it using the [Google API Console](https://console.cloud.google.com/). Google then provides information you'll need later, such as a client ID and a client secret.\n2. Activate the Google Street View Publish API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)\n3. When your application needs access to user data, it asks Google for a particular **scope** of access.\n4. Google displays a **consent screen** to the user, asking them to authorize your application to request some of their data.\n5. If the user approves, then Google gives your application a short-lived **access token**.\n6. Your application requests user data, attaching the access token to the request.\n7. If Google determines that your request and the token are valid, it returns the requested data.\n\nSome flows include additional steps, such as using **refresh tokens** to acquire new access tokens. For detailed information about flows for various types of applications, see Google's [OAuth 2.0 documentation](https://developers.google.com/identity/protocols/OAuth2).\n\nHere's the OAuth 2.0 scope information for the Google Street View Publish API:\n\n| Scope | Meaning |\n|-----------------------------------------------------|--------------------|\n| `https://www.googleapis.com/auth/streetviewpublish` | Read/write access. |\n\nTo request access using OAuth 2.0, your application needs the scope information, as well as\ninformation that Google supplies when you register your application (such as the client ID and the\nclient secret).\n\n**Tip:** The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check the [page with libraries and samples](/streetview/publish/libraries) for more details."]]
