Errors and Warnings

This page discusses the different types of errors and warnings that you may encounter when using the Display & Video 360 API.

API Errors

Requests made to the API that cannot be completed return an error message. Requests returning errors count against user quota and will be taken into consideration when reviewing requests for additional quota. Error responses should be processed and handled to avoid future errors.

An error response takes 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)
  }
}

Below is a list of common API errors along with the recommended action to take if they are returned:

Note: If the error persists even after taking the recommended action, contact support to report the issue.

Code	RPC	Recommended Action
400	INVALID_ARGUMENT	There is some issue with your request. Review the message field in the error response and modify your request accordingly.
401	UNAUTHENTICATED	Your request could not be properly authenticated. Verify that you are including valid OAuth credentials in your request. For more information on this, please reference our Getting Started guide.
403	PERMISSION_DENIED	You do not have the permissions needed to complete your request. Verify that your user account has the proper permissions for the relevant partner or advertiser.
404	NOT_FOUND	The resource you are attempting to retrieve cannot be found. Verify that the ID you are using is correct and for the resource type being retrieved.
409	ABORTED	The resource you are attempting to modify is being modified elsewhere. Wait a few seconds and then retry the request.
429	RESOURCE_EXHAUSTED	You have exceeded your rate limit or daily request quota. Examine your API usage using the Google API Console and modify your workflow to operate within the existing quota limits. For more information, please see our page on Quota Optimization. If your operations cannot be completed within your given daily quota, you may request additional quota.
500	INTERNAL	The API experienced an internal error. Wait a few seconds and then retry the request. If the error persists, contact support.
504	DEADLINE_EXCEEDED	The API took too long to complete the request. Wait a few seconds and then retry the request. If the error persists, contact support.

SDF Errors

The Display & Video 360 API uses an asynchronous method for generating and downloading structured data files (SDFs). For this reason, errors thrown during SDF generation are returned in the finished SDF download task. An SDF download task finishing in error is marked as done, but has a populated error field instead of a media resource name in the response field, as seen in this truncated example:

{
  ...
  "done": true,
  "error": {
    "code": 3,
    "message": "We couldn't prepare your CSV files: Invalid filter Ids for Advertiser: 00000000"
  }
}

If you receive an actionable error message when attempting to generate SDFs, you should follow it accordingly. If the error message is not clearly actionable, we recommend the following actions:

• Verify that your user has the proper permissions for the parent partner or advertiser resources.
• Confirm that the IDs provided in the filter are accurate, correspond to the intended resource type, and are within the context of the given root id.
• Ensure that you are not exceeding the limit of twenty concurrent SDF download tasks per user.

If you are still experiencing errors, contact support to report your issue.

Non-blocking Warnings

Non-blocking warnings are assigned to line items to indicate an issue that may impact a line item's serving. Similar warnings are communicated in the UI through a notification banner. These warnings are passive and are listed in a line item's warningMessages field.

Although passive, issues that cause these warnings can impact the serving of a line item to the point of fully preventing it altogether.

Prevention

Many issues that cause non-blocking warnings can be avoided through proper configuration of line item settings, including the following:

• Flight: If a line item's flight is invalid, or if the parent insertion order's flight is expired, the line item will generate a warning and won't serve. To avoid the latter issue, make sure that a line item's flight does not end later than the flight of its parent insertion order.
• Assigned creatives: If there is no valid creative assigned to a line item, the line item will generate a warning and will not serve.
• Targeting: If a line item's targeting is not properly assigned, the line item may generate a warning and serving may be impacted or prevented altogether.

If you are replicating configurations from an existing line item, ensure that the existing line item is not generating any unanticipated warnings.

Monitoring

Issues that cause non-blocking warnings may arise while a line item is in flight. In order to ensure that your line items are serving correctly, monitor your active line items for newly-generated warnings. Line items can be retrieved in bulk using the advertisers.lineItems.list function. If a line item is generating an unexpected warning, you should address the issue immediately to reduce the impact to serving.

Issues can arise even if a line item's settings or targeting have not changed. Examples include the pausing or expiring of the parent insertion order and the deprecation of user lists or other targeting.