AI-generated Key Takeaways
-
This API allows you to create new content or update existing content's metadata in Ad Manager.
-
Successful requests return the content, while failures return a
google.rpc.Code
. -
The API is deprecated, and new clients should use the AdManager Video API instead.
-
The HTTP request uses a PUT method to a URL containing network code, content source ID, and CMS content ID as path parameters.
-
The request and response bodies both contain an instance of
VideoContent
.
API to create new content or update its metadata if the content already exists in Ad Manager. Returns the content on success or a google.rpc.Code
on failure.
An example request looks like:
{
"status": "ACTIVE",
"title": "Best video ever",
"updateTime": "2019-01-24T01:30:15.01Z",
"duration": "230s",
"cuePoints": ["55.532s", "192s"],
"publishTime": "2019-01-24T01:30:15.01Z",
"thumbnailUrl": "http://www.domain.com/tn.jpg",
"metadata": {
"keyValues": {
"category": "sports",
"tag": ["soccer", "messi"],
"views": 700000,
"rating": 5.5
}
}
}
HTTP request
PUT https://contentingestion.googleapis.com/v1/{name=networks/*/sources/*/content/*}
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
name |
The resource name of the video content. VideoContent names have the form 'networks/{network_code}/sources/{content_source_id}/content/{cms_content_id}' The network code in Google Ad Manager to which this content belongs. The content source ID in Google Ad Manager to which this content should belong. The CMS content ID in Ad Manager, this is a required request parameter, formed as a part of the ad request to identify which ads Ad Manager can serve against the corresponding video. This value will be used for the vid parameter on a video ad request. It can be numeric or alphanumeric. |
Request body
The request body contains an instance of VideoContent
.
Response body
If successful, the response body contains an instance of VideoContent
.
Authorization Scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/contentingestion
For more information, see the OAuth 2.0 Overview.