Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Le richieste effettuate all'API Bid Manager che non possono essere completate restituiscono un errore
per creare un nuovo messaggio email. I messaggi di errore devono essere analizzati e gestiti in modo appropriato per evitare
futuri. Le richieste che restituiscono errori consumano la quota utente e i tassi di errore
vengono prese in considerazione durante l'esame
delle richieste per una quota aggiuntiva.
Una risposta di errore ha il formato seguente e include un codice di risposta HTTP,
un messaggio di errore e lo stato di un codice RPC di Google:
Di seguito è riportato un elenco di errori comuni relativi all'API, insieme alle azioni consigliate da intraprendere nel caso in cui
vengono restituiti:
Azioni consigliate per codice di errore e RPC
400INVALID_ARGUMENT
Si è verificato un problema con la tua richiesta.
Esamina il campo del messaggio nella risposta di errore e modifica la richiesta.
di conseguenza.
Se non riesci a trovare un
una combinazione accettabile di filtri, dimensioni e metriche, consulta le
migliore nei report
pratiche per i suggerimenti.
401UNAUTHENTICATED
La tua richiesta non può essere corretta
autenticati. Verifica di includere credenziali OAuth valide in
la tua richiesta. Per ulteriori informazioni, consulta
Come iniziare
.
404NOT_FOUND
La
Query
o
Report
che stai tentando di eseguire oppure impossibile trovare. Verifica il
seguenti:
Quota per le richieste API: esamina l'utilizzo dell'API utilizzando la proprietà
Google
Cloud Console e modificare il flusso di lavoro per operare all'interno
limiti di quota esistenti. Se le tue operazioni non possono essere completate entro
la quota giornaliera specificata,
richiedi ulteriori
di archiviazione.
[null,null,["Ultimo aggiornamento 2025-08-31 UTC."],[[["\u003cp\u003eBid Manager API request errors impact user quota and can be avoided by properly handling error messages.\u003c/p\u003e\n"],["\u003cp\u003eError responses provide specific codes, messages, and statuses to help diagnose and resolve issues.\u003c/p\u003e\n"],["\u003cp\u003eCommon errors include invalid arguments, authentication failures, resource exhaustion, and internal server errors.\u003c/p\u003e\n"],["\u003cp\u003eRecommended actions for common errors involve reviewing the request, verifying credentials, and adjusting API usage.\u003c/p\u003e\n"],["\u003cp\u003ePersistent errors after implementing recommended actions necessitate contacting support for further assistance.\u003c/p\u003e\n"]]],[],null,["# Errors\n\nRequests made to the Bid Manager API that can't be completed return an error\nmessage. Error messages should be parsed and appropriately handled to avoid\nfuture errors. Requests returning errors consume user quota, and error rates\nare considered when reviewing requests for additional quota.\n\nAn error response has the following format and includes an HTTP response code,\nan error message, and a [Google RPC code](//cloud.google.com/apis/design/errors#handling_errors) status: \n\n```gdscript\n{\n \"error\": {\n \"code\": integer,\n \"message\": string,\n \"status\": enum (google.rpc.Code)\n }\n}\n```\n\nHere's a list of common API errors along with the recommended action to take if\nthey are returned:\n| **Note:** If the error persists even after taking the recommended action, [contact\n| support](/bid-manager/support/contact) to report the issue.\n\n| Recommended Actions for error code and RPC ||\n|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `400` `INVALID_ARGUMENT` | There's an issue with your request. Review the message field in the error response, and modify your request accordingly. If you are experiencing issues with finding an acceptable combination of filters, dimensions, and metrics, refer to our [reporting best practices](/bid-manager/guides/general/best-practices) for recommendations. |\n| `401` `UNAUTHENTICATED` | Your request couldn't be properly authenticated. Verify that you are including valid OAuth credentials in your request. For more information, see the [Get Started guide](/bid-manager/guides/get-started/overview). |\n| `404` `NOT_FOUND` | The [`Query`](/bid-manager/reference/rest/current/queries#Query) or [`Report`](/bid-manager/reference/rest/current/queries.reports#Report) you are attempting to run or retrieve cannot be found. Verify the following: - The resource ID is correct - The resource type is valid for the endpoint - The resource in question was [created by the accessing user](/bid-manager/guides/general/best-practices#build_new_reports_in_the_ui_first) |\n| `429` `RESOURCE_EXHAUSTED` | You have exceeded either your [API request quota](/bid-manager/quotas) or [reporting quota](/bid-manager/guides/general/best-practices#consider_reporting_quotas). Read the error message to determine what type of quota you are exceeding: - API request quota: Examine your API usage using the [Google Cloud Console](//console.developers.google.com/project/_/apiui/apiview/doubleclickbidmanager.googleapis.com/metrics), and modify your workflow to operate within the existing quota limits. If your operations can't be completed within your given daily quota, [request additional quota](/bid-manager/quotas#additional_quota). - Reporting quota: Review [existing reporting quota best practices](/bid-manager/guides/general/best-practices#consider_reporting_quotas) and reach out to [Display \\& Video 360 product support](//support.google.com/displayvideo/contact/nghelp_contact_form) if needed. |\n| `500` `INTERNAL` | The API experienced an internal error. Use the [exponential backoff error handling strategy](/bid-manager/guides/general/best-practices#exponential_backoff) to wait and retry the request. If the error persists, [contact support](/bid-manager/support/contact). |\n| `504` `DEADLINE_EXCEEDED` | The API took too long to complete the request. Use the [exponential backoff error handling strategy](/bid-manager/guides/general/best-practices#exponential_backoff) to wait and retry the request. If the error persists, [contact support](/bid-manager/support/contact). |"]]
