AI-generated Key Takeaways
- 
          Display & Video 360 API v3 has sunset and users should use v4 instead. 
- 
          The information provided covers creating a new campaign using an HTTP POST request. 
- 
          Key details covered include the HTTP request format, path parameters, request and response body structures, and required authorization scopes. 
- 
          The request body requires an instance of Campaign, and the response body returns a newly created Campaign if successful. 
Creates a new campaign. Returns the newly created campaign if successful.
HTTP request
POST https://displayvideo.googleapis.com/v3/advertisers/{campaign.advertiserId}/campaigns
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| campaign.advertiserId | 
 Output only. The unique ID of the advertiser the campaign belongs to. | 
Request body
The request body contains an instance of Campaign.
Response body
If successful, the response body contains a newly created instance of Campaign.
Authorization scopes
Requires one of the following OAuth scopes:
- https://www.googleapis.com/auth/display-video
- https://www.googleapis.com/auth/display-video-mediaplanning
For more information, see the OAuth 2.0 Overview.