Page Summary
-
References can be created by uploading a video/audio file or a pre-generated fingerprint, or by using a claimed video's content via the
claimIdparameter. -
HTTP requests for uploading media content use the
POST https://youtubepartner.googleapis.com/upload/youtube/partner/v1/referencesURI, while metadata-only requests usePOST https://youtubepartner.googleapis.com/youtube/partner/v1/references. -
The
onBehalfOfContentOwnerquery parameter specifies the content owner the user is acting on behalf of, supporting users associated with multiple content owners. -
The request body is an instance of the
Reference, and if the request is successful, the response body will also contain an instance ofReference. -
The
https://www.googleapis.com/auth/youtubepartnerOAuth scope is required for authorization.
Creates a reference in one of the following ways:
- If your request is uploading a reference file, YouTube creates the reference from the provided content. You can provide either a video/audio file or a pre-generated fingerprint. If you are providing a pre-generated fingerprint, set the
referenceresource's fpDirect property totruein the request body. In this flow, you can use either the multipart or resumable upload flows to provide the reference content. - If you want to create a reference using a claimed video as the reference content, use the
claimIdparameter to identify the claim.
HTTP request
- Upload URI, for media upload requests:
POST https://youtubepartner.googleapis.com/upload/youtube/partner/v1/references - Metadata URI, for metadata-only requests:
POST https://youtubepartner.googleapis.com/youtube/partner/v1/references
The URL uses gRPC Transcoding syntax.
Query parameters
| Parameters | |
|---|---|
claimId
|
The |
onBehalfOfContentOwner
|
The |
Request body
The request body contains an instance of Reference
.
Response body
If successful, the response body contains an instance of Reference
.
Authorization scopes
Requires the following OAuth scope:
-
https://www.googleapis.com/auth/youtubepartner
For more information, see the OAuth 2.0 Overview .

