Response Codes in the Search Ads 360 API
Stay organized with collections
Save and categorize content based on your preferences.
If a request to the Search Ads 360 API is successful, the API returns
a 200
HTTP status code along with the requested data in the body of the response.
If a request fails to validate, the API returns an HTTP status code between
400
and 499
along with a description of the validation error.
If you send a valid Report.get()
request but Search Ads 360 is unable to generate a report, the API returns
one of the HTTP status codes described below.
Code |
Reason |
Description |
Recommended action |
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. |
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.
Include your developer project ID, and the Code and Reason from this table row
(and not the one below).
|
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 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.
|
410 |
reportUnavailableInternalServerError |
Search Ads 360 is unable to return or generate the report for some unexpected reason. |
Contact Search Ads
360 customer support. Include your report ID.
|
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. Include your report ID. |
400 |
unsupportedApiVersion |
Version not supported. |
Migrate to the Search Ads 360 Reporting API. |
For all other types of errors, the API returns
Standard Error Responses.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[null,null,["Last updated 2025-08-28 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)."]]