Search Ads 360 Reporting API versi sebelumnya tidak digunakan lagi. Sekarang Anda dapat membuat laporan menggunakan Search Ads 360 Reporting API baru.
Perhatikan bahwa metode get dan getByCustomerId di Search Ads 360 Conversion API tidak digunakan lagi pada Kuartal 3 2025. Untuk terus mengakses data konversi, Anda harus membuat laporan menggunakan resource konversi menggunakan Search Ads 360 Reporting API versi baru. Lihat detail selengkapnya di sini.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Jika permintaan ke Search Ads 360 API berhasil, API akan menampilkan kode status HTTP 200 beserta data yang diminta dalam isi respons.
Jika permintaan gagal divalidasi, API akan menampilkan kode status HTTP antara
400 dan 499 beserta deskripsi error validasi.
Jika Anda mengirim permintaan Report.get()
yang valid, tetapi Search Ads 360 tidak dapat membuat laporan, API akan menampilkan
salah satu kode status HTTP yang dijelaskan di bawah.
Kode
Alasan
Deskripsi
Tindakan yang disarankan
410
reportUnavailableRequestTooLarge
Laporan tidak lagi diproses karena terlalu besar.
Minta beberapa laporan yang lebih kecil. Misalnya, bagi satu laporan pengiklan
menjadi beberapa laporan akun mesin. Atau bagi laporan selama setahun menjadi laporan selama 12
bulan.
410
reportUnavailableRateLimitExceeded
Laporan tidak lagi diproses karena terlalu banyak laporan yang diminta oleh project developer dalam waktu singkat.
Pastikan klien Anda tidak mengirim permintaan lebih sering dari yang Anda inginkan.
Jika klien Anda berperforma seperti yang diharapkan,
hubungi dukungan pelanggan Search Ads 360.
Sertakan project ID developer Anda, serta Kode dan Alasan dari baris tabel ini
(bukan yang di bawah).
410
reportUnavailableQuotaExceeded
Laporan tidak lagi diproses karena terlalu banyak data yang diminta oleh project developer hari ini.
Pastikan klien Anda tidak mengirim permintaan yang lebih besar dari yang Anda inginkan. Anda dapat melacak penggunaan kuota di Google Cloud Console.
Jika klien Anda berperforma seperti yang diharapkan,
hubungi dukungan pelanggan
Search Ads 360 dan minta penambahan kuota. Sertakan ID project developer Anda, serta Kode dan Alasan dari baris tabel ini (bukan baris di atas).
Meskipun permintaan lulus validasi, Search Ads 360 tidak dapat membuat laporan yang diminta
karena berisi kombinasi kolom, filter, dan segmentasi yang tidak valid.
[[["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 2024-12-05 UTC."],[[["\u003cp\u003eSearch Ads 360 API returns a \u003ccode\u003e200\u003c/code\u003e HTTP status code for successful requests and a status code between \u003ccode\u003e400\u003c/code\u003e and \u003ccode\u003e499\u003c/code\u003e for validation failures.\u003c/p\u003e\n"],["\u003cp\u003eIf a valid report request cannot be generated, the API returns a \u003ccode\u003e410\u003c/code\u003e status code with a specific reason, such as the report being too large, rate limit exceeded, or internal server error.\u003c/p\u003e\n"],["\u003cp\u003eFor report generation failures, recommended actions include requesting smaller reports, checking client request frequency, contacting support for quota increases, or reviewing report configurations.\u003c/p\u003e\n"],["\u003cp\u003eThe API provides detailed descriptions and recommended actions for each type of report generation failure, helping users troubleshoot and resolve issues effectively.\u003c/p\u003e\n"],["\u003cp\u003eFor other errors, refer to the Standard Error Responses documentation for guidance.\u003c/p\u003e\n"]]],["Successful Search Ads 360 API requests return a `200` status code. Validation failures result in `400-499` codes, with error descriptions. If report generation fails, `410` codes indicate issues like excessive size, rate limits, quota overages, internal errors, or invalid report specifications; each with specific resolution steps. A `400` error indicates an unsupported API version. Other errors follow standard error responses.\n"],null,["# Response Codes in the Search Ads 360 API\n\nIf a request to the Search Ads 360 API is **successful** , the API returns\na `200` HTTP status code along with the requested data in the body of the response.\n\nIf a request **fails to validate** , the API returns an HTTP status code between\n`400` and `499` along with a description of the validation error.\n\nIf you send a valid [`Report.get()`](/search-ads/v2/reference/reports/get)\nrequest but Search Ads 360 is **unable to generate a report**, the API returns\none of the HTTP status codes described below.\n\n| Code | Reason | Description | Recommended action |\n|------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 410 | reportUnavailableRequestTooLarge | The report is no longer being processed because the report is too large. | Request multiple smaller reports instead. For example, break a single advertiser report into multiple engine account reports. Or break a year-long report into 12 month long reports. |\n| 410 | reportUnavailableRateLimitExceeded | The report is no longer being processed because too many reports were requested by the developer project in a short amount of time. | Make sure your client isn't sending requests more frequently than you intend. If your client is performing as expected, [contact Search Ads 360 customer support](https://support.google.com/searchads/answer/3280641). Include your developer project ID, and the Code and Reason from this table row (and not the one below). |\n| 410 | reportUnavailableQuotaExceeded | The report is no longer being processed because too much data has been requested by the developer project today. | Make sure your client isn't sending larger requests than you intend. You can keep track of your quota usage in Google Cloud Console. If your client is performing as expected, [contact Search Ads 360 customer support](https://support.google.com/searchads/answer/9026876) and ask for a quota increase. Include your developer project ID, and the Code and Reason from this table row (and not the one above). Also see [Pricing and Usage Limits](/pricing). |\n| 410 | reportUnavailableInternalServerError | Search Ads 360 is unable to return or generate the report for some unexpected reason. | [Contact Search Ads 360 customer support](https://support.google.com/searchads/answer/9026876). Include your report ID. |\n| 410 | reportUnavailableRequestError | Even though the request passed validation, Search Ads 360 cannot generate the requested report because it contains an invalid combination of columns, filters, and segmentations. | [Contact Search Ads 360 customer support](https://support.google.com/searchads/answer/9026876). Include your report ID. |\n| 400 | unsupportedApiVersion | Version not supported. | Migrate to the Search Ads 360 Reporting API. |\n\nFor all other types of errors, the API returns\n[Standard Error Responses](/search-ads/v2/standard-error-responses)."]]
