AI-generated Key Takeaways
-
Display & Video 360 API v3 has sunset and users should use v4 instead.
-
The HTTP request to get a campaign is
GET https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}/campaigns/{campaignId}. -
Both the
advertiserIdandcampaignIdare required path parameters. -
A successful request returns a Campaign instance in the response body.
-
One of two specific OAuth scopes is required for authorization.
Gets a campaign.
HTTP request
GET https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}/campaigns/{campaignId}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
advertiserId
|
Required. The ID of the advertiser this campaign belongs to. |
campaignId
|
Required. The ID of the campaign to fetch. |
Request body
The request body must be empty.
Response body
If successful, the response body contains an 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 .
