Errors

AI-generated Key Takeaways

outlined_flag

• Bid Manager API requests that fail return an error message which should be parsed and handled to avoid future errors.

• Error responses include an HTTP response code, an error message, and a Google RPC code status.

• Different error codes and RPC statuses indicate specific issues and have recommended actions to resolve them, such as modifying the request for 400 INVALID_ARGUMENT or checking authentication for 401 UNAUTHENTICATED .

• Errors like 429 RESOURCE_EXHAUSTED indicate exceeding API or reporting quotas, requiring workflow adjustments or quota requests.

• For internal or timeout errors ( 500 INTERNAL , 504 DEADLINE_EXCEEDED ), retrying with exponential backoff is recommended before contacting support if the issue persists.

Requests made to the Bid Manager API that can't be completed return an error message. Error messages should be parsed and appropriately handled to avoid future errors. Requests returning errors consume user quota, and error rates are considered when reviewing requests for additional quota.

An error response has the following format and includes an HTTP response code, an error message, and a Google RPC code status:

 { 
  
 "error" 
 : 
  
 { 
  
 "code" 
 : 
  
 integer 
 , 
  
 "message" 
 : 
  
 string 
 , 
  
 "status" 
 : 
  
 enum 
  
 ( 
 google 
 . 
 rpc 
 . 
 Code 
 ) 
  
 } 
 } 

Here's a list of common API errors along with the recommended action to take if they are returned: