AI-generated Key Takeaways
-
Display & Video 360 API v3 has sunset and users should transition to v4.
-
The
GET
request to fetch a partner uses a specific URL structure with a requiredpartnerId
path parameter. -
The request body for fetching a partner must be empty.
-
A successful response will contain details about the partner in the response body.
-
This operation requires specific OAuth authorization scopes.
Gets a partner.
HTTP request
GET https://displayvideo.googleapis.com/v3/partners/{partnerId}
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
partnerId |
Required. The ID of the partner to fetch. |
Request body
The request body must be empty.
Response body
If successful, the response body contains an instance of Partner
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.