A partir de 8 de setembro de 2025, todos os novos itens de linha precisarão declarar se vão veicular anúncios políticos da União Europeia (UE). As APIs do Display & Video 360 e os uploads de SDF que não fornecem declarações vão falhar. Consulte nossa página de suspensões de uso para mais detalhes sobre como atualizar sua integração e fazer essa declaração.
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Muitos métodos da API Display & Video 360 realizam operações complexas que podem levar mais do que
alguns segundos para serem concluídas. Às vezes, as solicitações para esses métodos podem exceder
a latência esperada, causando erros na API ou no lado do cliente. Esta página lista
práticas para lidar com problemas causados pela latência de solicitação estendida.
Aumento do tempo limite padrão na biblioteca de cliente
Alguns métodos específicos foram rotulados na documentação de referência
como excedendo regularmente a latência esperada. Outros métodos também podem apresentar
comportamento de alta latência periodicamente.
Os limites de tempo limite padrão para algumas bibliotecas de cliente podem resultar em erros ao
fazer solicitações de alta latência. Os tempos limite padrão para um subconjunto de bibliotecas de cliente
com suporte são:
Java: 20 segundos
Python: 60 segundos
PHP: 60 segundos
É possível evitar os limites de tempo do lado do cliente aumentando esses limites padrão. Siga
estas instruções para ajustar o tempo limite padrão da biblioteca de cliente durante
a execução:
/** * Adjusts HTTP timeout values used by the provided request initializer. * * @param requestInitializer The {@link HttpRequestInitializer} used to authorize requests. * @param newHttpTimeout The HTTP timeout for requests in seconds. * @return An {@link HttpRequestInitializer} with modified HTTP timeout values. */privatestaticHttpRequestInitializersetHttpTimeout(finalHttpRequestInitializerrequestInitializer,finalintnewHttpTimeout){returnnewHttpRequestInitializer(){@Overridepublicvoidinitialize(HttpRequesthttpRequest)throwsIOException{requestInitializer.initialize(httpRequest);httpRequest.setConnectTimeout(newHttpTimeout*1_000);httpRequest.setReadTimeout(newHttpTimeout*1_000);}};}
Chamar a função ao criar o cliente da API Display & Video 360.
// Create authorized API client with non-default timeouts.DisplayVideoservice=newDisplayVideo.Builder(credential.getTransport(),credential.getJsonFactory(),setHttpTimeout(credential,http-timeout-in-seconds)).setApplicationName("displayvideo-java-installed-app-sample").build();
Python
Importar o módulo HTTP da biblioteca de cliente Python da API do Google.
# Build the API service.service=discovery.build('displayvideo','v3',discoveryServiceUrl=discovery_url,credentials=credentials)
PHP
Faça o download e instale a biblioteca HTTP do Guzzle usando o
Composer.
composerrequireguzzlehttp/guzzle:^7.0
Criar um cliente HTTP do Guzzle, atribuindo o valor do tempo limite.
$httpClient = new \GuzzleHttp\Client(['timeout' => http-timeout-in-seconds]);
Crie o cliente do Google e atribua o cliente HTTP do Guzzle.
$client = new Google_Client();$client->setHttpClient($httpClient);
Processar erros de tempo limite da API
Em casos raros, as solicitações que concluem operações complexas podem exceder o
tempo limite do servidor de 180 segundos, fazendo com que a API retorne uma resposta de erro 408 ou
504.
Se uma solicitação responder com um desses códigos de erro, recomendamos que você
tente novamente usando a estratégia de espera exponencial.
[null,null,["Última atualização 2025-07-25 UTC."],[[["\u003cp\u003eSome Display & Video 360 API methods might take longer to complete, potentially leading to errors due to request latency.\u003c/p\u003e\n"],["\u003cp\u003eYou can increase the default timeout in your client library (Java, Python, or PHP) to avoid client-side timeout errors.\u003c/p\u003e\n"],["\u003cp\u003eThe Display & Video 360 API has a server-side timeout of 180 seconds, after which it will return a \u003ccode\u003e408\u003c/code\u003e or \u003ccode\u003e504\u003c/code\u003e error.\u003c/p\u003e\n"],["\u003cp\u003eIf a request exceeds the server-side timeout, retry it using exponential backoff and contact support if the issue persists.\u003c/p\u003e\n"]]],["The core issue addressed is managing request latency with the Display & Video 360 API, where some operations may take longer than expected. To prevent client-side timeout errors, it is recommended to increase the default timeout in the client library. The provided examples show how to adjust timeout settings in Java, Python, and PHP. In the rare case that requests exceed the API's 180-second server-side timeout, resulting in `408` or `504` errors, the advice is to retry with exponential backoff and contact support if problems continue.\n"],null,["# Configure timeouts and retries\n\nMany Display \\& Video 360 API methods perform complex operations that might take longer than\na few seconds to complete. Requests to these methods can sometimes exceed\nexpected latency, causing errors on the API or client side. This page lists\npractices for handling issues caused by extended request latency.\n\nIncrease default timeout in client library\n------------------------------------------\n\nA handful of specific methods have been labeled in their reference documentation\nas regularly exceeding expected latency. Other methods could also exhibit\nhigh-latency behavior periodically.\n\nThe default timeout limits for some client libraries could result in errors when\nmaking high-latency requests. Default timeouts for a subset of supported client\nlibraries are:\n\n- **Java**: 20 seconds\n- **Python**: 60 seconds\n- **PHP**: 60 seconds\n\nClient-side timeouts can be avoided by raising these default timeouts. Follow\nthese instructions to adjust the default timeout for your client library during\nruntime:\n**Caution:** The Display \\& Video 360 API has a server-side timeout value of 180 seconds. If a request lasts longer than 180 seconds, the API will return an error. \n\n### Java\n\n1. **Import necessary resources.**\n\n import com.google.api.client.http.HttpRequest;\n import com.google.api.client.http.HttpRequestInitializer;\n import java.io.IOException;\n\n2. **Build function for setting HTTP timeout.**\n\n /**\n * Adjusts HTTP timeout values used by the provided request initializer.\n *\n * @param requestInitializer The {@link HttpRequestInitializer} used to authorize requests.\n * @param newHttpTimeout The HTTP timeout for requests in seconds.\n * @return An {@link HttpRequestInitializer} with modified HTTP timeout values.\n */\n private static HttpRequestInitializer setHttpTimeout(\n final HttpRequestInitializer requestInitializer,\n final int newHttpTimeout) {\n return new HttpRequestInitializer() {\n @Override\n public void initialize(HttpRequest httpRequest) throws IOException {\n requestInitializer.initialize(httpRequest);\n httpRequest.setConnectTimeout(newHttpTimeout * 1_000);\n httpRequest.setReadTimeout(newHttpTimeout * 1_000);\n }\n };\n }\n\n3. **Call function when creating the Display \\& Video 360 API client.**\n\n // Create authorized API client with non-default timeouts.\n DisplayVideo service =\n new DisplayVideo.Builder(\n credential.getTransport(),\n credential.getJsonFactory(),\n setHttpTimeout(credential, \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ehttp\u003c/span\u003e\u003cspan class=\"devsite-syntax-o\"\u003e-\u003c/span\u003e\u003cspan class=\"devsite-syntax-n\"\u003etimeout\u003c/span\u003e\u003cspan class=\"devsite-syntax-o\"\u003e-\u003c/span\u003e\u003cspan class=\"devsite-syntax-n\"\u003ein\u003c/span\u003e\u003cspan class=\"devsite-syntax-o\"\u003e-\u003c/span\u003e\u003cspan class=\"devsite-syntax-n\"\u003eseconds\u003c/span\u003e\u003c/var\u003e)\n )\n .setApplicationName(\"displayvideo-java-installed-app-sample\")\n .build();\n\n### Python\n\n1. **Import Google API Python client library http module.**\n\n from googleapiclient import http\n\n2. **Update default timeout constant.**\n\n http.DEFAULT_HTTP_TIMEOUT_SEC = \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ehttp\u003c/span\u003e\u003cspan class=\"devsite-syntax-o\"\u003e-\u003c/span\u003e\u003cspan class=\"devsite-syntax-n\"\u003etimeout\u003c/span\u003e\u003cspan class=\"devsite-syntax-o\"\u003e-\u003c/span\u003e\u003cspan class=\"devsite-syntax-ow\"\u003ein\u003c/span\u003e\u003cspan class=\"devsite-syntax-o\"\u003e-\u003c/span\u003e\u003cspan class=\"devsite-syntax-n\"\u003eseconds\u003c/span\u003e\u003c/var\u003e\n\n3. **Build API service.**\n\n # Build the API service.\n service = discovery.build(\n 'displayvideo',\n 'v3',\n discoveryServiceUrl=discovery_url,\n credentials=credentials)\n\n### PHP\n\n1. **Download and install the Guzzle HTTP library using\n [Composer](//getcomposer.org/).**\n\n composer require guzzlehttp/guzzle:^7.0\n\n2. **Create Guzzle HTTP client, assigning timeout value.**\n\n $httpClient = new \\GuzzleHttp\\Client(['timeout' =\u003e \u003cvar translate=\"no\"\u003ehttp-timeout-in-seconds\u003c/var\u003e]);\n\n3. **Create Google client and assign Guzzle HTTP client.**\n\n $client = new Google_Client();\n $client-\u003esetHttpClient($httpClient);\n\nHandle API timeout errors\n-------------------------\n\nIn rare cases, requests completing complex operations could exceed the\nserver-side timeout of 180 seconds, causing the API to return a `408` or `504`\nerror response.\n\nIf a request responds with either of these error codes, we recommend that you\nretry these requests using the [exponential backoff strategy](/display-video/api/guides/how-tos/upload#exp-backoff).\n\nIf the error persists, reach out to support using the [contact form](/display-video/api/support/contact)."]]