Mulai 8 September 2025, setiap item baris baru harus menyatakan apakah item baris tersebut akan menayangkan iklan politik Uni Eropa (EU) atau tidak. Upload SDF dan API Display & Video 360 yang tidak memberikan pernyataan akan gagal. Lihat halaman penghentian penggunaan kami untuk mengetahui detail selengkapnya tentang cara memperbarui integrasi Anda untuk membuat pernyataan ini.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Batas penggunaan melindungi infrastruktur Google dari proses otomatis yang menggunakan
Display & Video 360 API dengan cara yang tidak tepat. Kebijakan ini memastikan bahwa tindakan
satu developer tidak dapat berdampak negatif pada komunitas yang lebih besar.
Batas kuota permintaan API
Display & Video 360 API menggunakan dua jenis batas:
Total batas kuota, yang dihitung berdasarkan semua permintaan yang relevan.
Batas kuota tulis, yang diperhitungkan oleh semua permintaan relevan yang dibuat untuk menulis metode. Metode tulis ditentukan sebagai metode—seperti create,
patch, delete, atau bulkEdit—yang mengubah resource. Perhatikan bahwa beberapa
metode menggunakan lebih banyak kuota tulis daripada metode lainnya.
Total permintaan per menit per pengiklan per project:300
Permintaan tulis per menit per pengiklan per project:150
Metode yang intensif menulis
Metode API berikut intensif penulisan, yang berarti metode tersebut menggunakan
resource produk dalam jumlah yang signifikan dan, akibatnya, menggunakan lebih banyak
kuota permintaan tulis daripada permintaan tulis lainnya.
Permintaan yang dibuat ke metode yang intensif menulis dihitung sebagai 5 kueri tulis
saat menghitung penggunaan kuota permintaan tulis. Misalnya, 100 permintaan tulis standar dan 21 permintaan intensif tulis (tidak satu pun yang menentukan pengiklan) yang dilakukan dalam satu menit akan dihitung sebagai 205 kueri tulis (100 + (21 * 5) =
205) dan akan melebihi batas kuota permintaan umum yang ada sebesar 200 kueri tulis per menit.
Jika permintaan Anda gagal karena melebihi batas permintaan API, API akan menampilkan kode status HTTP dan alasan error.
Selain itu, isi respons berisi deskripsi mendetail tentang hal yang menyebabkan error.
Daftar berikut menunjukkan kemungkinan error dan tindakan yang direkomendasikan untuk
kegagalan permintaan yang disebabkan oleh melampaui batas permintaan API.
Kode
PPK
Pesan
Tindakan yang Disarankan
429
RESOURCE_EXHAUSTED
Resource telah
habis
(misalnya, periksa
kuota).
Periksa penggunaan Anda
dari Konsol Google API dan
ubah alur kerja Anda untuk lebih
memparalelkan permintaan yang dibuat di bawah
pengiklan yang berbeda atau secara
umum memperlambat kecepatan
Anda mengirim permintaan.
Peningkatan tidak dapat diminta untuk batas kuota API Display & Video 360.
[[["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\u003eDisplay & Video 360 API usage is subject to quota limits to protect Google's infrastructure and ensure fair usage.\u003c/p\u003e\n"],["\u003cp\u003eTwo main quota types exist: total requests and write requests (methods modifying resources), with limits applied per project and per advertiser per project.\u003c/p\u003e\n"],["\u003cp\u003eCertain write-intensive methods consume more write quota than others.\u003c/p\u003e\n"],["\u003cp\u003eExceeding quota limits can lead to request throttling, indicated by a 429 error code, requiring adjustments to request frequency.\u003c/p\u003e\n"],["\u003cp\u003eQuota limit increases for the Display & Video 360 API are not available.\u003c/p\u003e\n"]]],[],null,["# Usage Limits\n\nUsage limits protect Google's infrastructure from automated processes that use\nthe Display \\& Video 360 API in an inappropriate way. They ensure that one developer's\nactions can't negatively impact the larger community.\n\nAPI request quota limits\n------------------------\n\nThe Display \\& Video 360 API uses two types of limits:\n\n- **Total quota limits**, which all relevant requests count against.\n- **Write quota limits** , which all relevant requests made to write methods count against. Write methods are defined as methods---such as `create`, `patch`, `delete`, or `bulkEdit`---that modify resources. Note that [some\n methods](#write_intensive) consume more write quota than others.\n\nIf your project exceeds any of these limits, [throttling could\noccur](#exceeding_limits).\n\n### Project-wide quota limit\n\nThe following default quota limits are shared by all Display \\& Video 360 API resources\nand methods:\n\n- **Total requests per minute per project:** `1500`\n- **Write requests per minute per project:** `700`\n\n### Advertiser-specific request quota limits\n\nMethods that specify an advertiser ID in the request URL count against\nadditional \"per advertiser per project\" quota limits.\n\nAll requests with an advertiser ID specified in their URL path---such as\nthose to the [`advertisers.lineItems`](/display-video/api/reference/rest/current/advertisers.lineItems),\n[`advertisers.creatives`](/display-video/api/reference/rest/current/advertisers.creatives), or\n[`advertisers.channels`](/display-video/api/reference/rest/current/advertisers.channels) services---will count against\nthe following quota limits:\n\n- **Total requests per minute per advertiser per project:** `300`\n- **Write requests per minute per advertiser per project:** `150`\n\nWrite-intensive methods\n-----------------------\n\nThe following API methods are write-intensive, meaning that they use a\nsignificant amount of product resources and, as a result, consume more\nwrite request quota than other write requests.\n\nRequests made to write-intensive methods are counted as 5 write queries\nwhen computing write request quota consumption. For example, 100 standard write\nrequests and 21 write-intensive requests (none of which specify an advertiser)\nmade within a minute would be counted as 205 write queries (`100 + (21 * 5) =\n205`) and would exceed the existing general request quota limit of 200 write\nqueries per minute.\n\nThe following methods are considered write-intensive:\n\n- [`customBiddingAlgorithms.scripts.create`](/display-video/api/reference/rest/current/customBiddingAlgorithms.scripts/create)\n- [`customBiddingAlgorithms.uploadScript`](/display-video/api/reference/rest/current/customBiddingAlgorithms/uploadScript)\n- [`firstPartyAndPartnerAudiences.create`](/display-video/api/reference/rest/current/firstPartyAndPartnerAudiences/create)\n- [`firstPartyAndPartnerAudiences.editCustomerMatchMembers`](/display-video/api/reference/rest/current/firstPartyAndPartnerAudiences/editCustomerMatchMembers)\n- [`media.upload`](/display-video/api/reference/rest/current/media/upload)\n\nExceeding quota limits\n----------------------\n\nIn the unlikely event that your request fails due to exceeding an API request\nlimit, the API returns an HTTP status code and reason for the error.\nAdditionally, the body of the response contains a detailed description of what\ncaused the error.\n\nThe following list shows the possible errors and recommended actions for\nrequest failures caused by exceeding API request limits.\n\n| Code | RPC | Message | Recommended Action |\n|-------|----------------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `429` | `RESOURCE_EXHAUSTED` | Resource has been exhausted (e.g., check quota). | [Examine your usage](//console.developers.google.com/project/_/apiui/apiview/displayvideo.googleapis.com/metrics) from the Google API Console and modify your workflow to better parallelize requests made under different advertisers or more generally slow down the rate at which you are sending requests. |\n\nIncreases cannot be requested for Display \\& Video 360 API quota limits."]]