Mengizinkan Permintaan
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat aplikasi Anda meminta data pribadi, permintaan tersebut harus diizinkan oleh
yang memiliki akses ke data tersebut.
Setiap permintaan yang dikirimkan aplikasi Anda ke Bid Manager API harus menyertakan token otorisasi. Token
juga mengidentifikasi aplikasi Anda ke Google.
Tentang protokol otorisasi
Aplikasi Anda harus menggunakan OAuth 2.0 untuk mengizinkan permintaan.
Tidak ada protokol otorisasi lain yang didukung. Jika aplikasi Anda menggunakan Login dengan Google, beberapa aspek otorisasi akan ditangani untuk
maksimal.
Mengizinkan permintaan dengan OAuth 2.0
Semua permintaan ke Bid Manager API harus diizinkan oleh pengguna terautentikasi.
Detail proses otorisasi, atau "alur", untuk OAuth 2.0 agak bervariasi tergantung
pada jenis aplikasi apa yang Anda tulis. Proses umum berikut berlaku untuk semua jenis aplikasi:
- Saat membuat aplikasi, Anda mendaftarkannya menggunakan Konsol API Google. Google kemudian memberikan informasi yang diperlukan
seperti ID klien dan rahasia klien.
- Mengirimkan verifikasi OAuth
meninjau aplikasi Anda agar dapat mengakses cakupan API Bid Manager.
- Aktifkan Bid Manager API di Konsol API Google. (Jika API tidak tercantum dalam
Konsol API, lalu lewati langkah ini.)
- Saat memerlukan akses ke data pengguna, aplikasi Anda akan meminta cakupan tertentu dari
akses.
- Google menampilkan layar izin kepada pengguna, yang meminta mereka untuk mengizinkan aplikasi Anda untuk
akses ke beberapa data mereka.
- Jika pengguna menyetujui, Google akan memberi aplikasi Anda token akses berumur singkat.
- Aplikasi Anda meminta data pengguna, dengan melampirkan token akses ke permintaan.
- Jika Google menentukan bahwa permintaan Anda dan token tersebut valid, data yang diminta akan ditampilkan.
Beberapa alur menyertakan langkah tambahan, seperti menggunakan token refresh untuk mendapatkan akses baru
token kata. Guna mengetahui informasi mendetail tentang alur untuk berbagai jenis aplikasi, lihat dokumentasi OAuth 2.0 Google.
Cakupan OAuth
Berikut adalah informasi cakupan OAuth 2.0 untuk Bid Manager API:
| Cakupan |
Arti |
https://www.googleapis.com/auth/doubleclickbidmanager |
Akses baca/tulis. |
Untuk meminta akses menggunakan OAuth 2.0, aplikasi Anda memerlukan informasi cakupan, serta
informasi yang diberikan oleh Google saat Anda mendaftarkan aplikasi Anda (seperti client ID dan
rahasia klien).
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-25 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-25 UTC."],[[["\u003cp\u003eApplications need authorization from an authenticated user to access private data through the Bid Manager API.\u003c/p\u003e\n"],["\u003cp\u003eThe Bid Manager API exclusively supports OAuth 2.0 for authorization and requires apps to pass an OAuth verification review.\u003c/p\u003e\n"],["\u003cp\u003eApps must be registered using the Google API Console, undergo an OAuth verification review, and request specific scopes for data access.\u003c/p\u003e\n"],["\u003cp\u003eUpon user consent, Google provides a short-lived access token which the app uses to make authorized requests for user data.\u003c/p\u003e\n"]]],["Apps requesting private data through the Bid Manager API must be authorized by an authenticated user via OAuth 2.0. The process involves registering the app with Google, submitting an OAuth verification request, and activating the API. The app then requests a specific access scope, prompting a user consent screen. Upon approval, Google issues a short-lived access token. This token is included in data requests, allowing Google to validate the request and return data. The available scope is for read/write access.\n"],null,["# Authorize Requests\n\nWhen your app requests private data, the request must be authorized by an authenticated\nuser who has access to that data.\n| **Note:** If your app accesses the Bid Manager API, it must pass the [OAuth verification review](//support.google.com/cloud/answer/7454865#verification). If you see **unverified app** on the screen when testing your app, you must submit a verification request to remove it. Learn more about [unverified apps](//support.google.com/cloud/answer/7454865) or get answers to [frequently asked questions about app\n| verification](//support.google.com/cloud/answer/9110914).\n\nEvery request your app sends to the Bid Manager API must include an authorization token. The token\nalso identifies your app to Google.\n\nAbout authorization protocols\n-----------------------------\n\nYour app must use [OAuth 2.0](/identity/protocols/OAuth2) to authorize requests.\nNo other authorization protocols are supported. If your app uses [Google Sign-In](/identity#google-sign-in), some aspects of authorization are handled for\nyou.\n\nAuthorizing requests with OAuth 2.0\n-----------------------------------\n\nAll requests to the Bid Manager API must be authorized by an authenticated user.\n\nThe details of the authorization process, or \"flow,\" for OAuth 2.0 vary somewhat depending\non what kind of app you're writing. The following general process applies to all app types:\n\n1. When you create your app, 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. Submit an [OAuth verification\n review](//support.google.com/cloud/answer/7454865#verification) request for your app in order to access the Bid Manager API scope.\n3. Activate the Bid Manager API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)\n4. When your app needs access to user data, it asks Google for a particular **scope** of access.\n5. Google displays a **consent screen** to the user, asking them to authorize your app for access to some of their data.\n6. If the user approves, then Google gives your app a short-lived **access token**.\n7. Your app requests user data, attaching the access token to the request.\n8. 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\ntokens. For detailed information about flows for various types of apps, see Google's [OAuth 2.0 documentation](/identity/protocols/OAuth2).\n\nOAuth scope\n-----------\n\nHere's the OAuth 2.0 scope information for the Bid Manager API:\n\n| Scope | Meaning |\n|---------------------------------------------------------|--------------------|\n| `https://www.googleapis.com/auth/doubleclickbidmanager` | Read/write access. |\n\nTo request access using OAuth 2.0, your app needs the scope information, as well as\ninformation that Google supplies when you register your app (such as the client ID and the\nclient secret)."]]
