AI-generated Key Takeaways
-
Display & Video 360 API v3 has sunset and users should use v4 instead.
-
The method to create a new advertiser can experience high latency, so increasing your default timeout is recommended.
-
The request uses a POST HTTP method to
https://displayvideo.googleapis.com/v3/advertisers
. -
The request and response bodies contain an instance of Advertiser.
-
Authorization requires the
https://www.googleapis.com/auth/display-video
OAuth scope.
Creates a new advertiser. Returns the newly created advertiser if successful.
This method regularly experiences high latency. We recommend increasing your default timeout to avoid errors.
HTTP request
POST https://displayvideo.googleapis.com/v3/advertisers
The URL uses gRPC Transcoding syntax.
Request body
The request body contains an instance of Advertiser
.
Response body
If successful, the response body contains a newly created instance of Advertiser
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.