REST Resource: assetShares
Stay organized with collections
Save and categorize content based on your preferences.
Resource: AssetShare
An assetShare
resource, which is only relevant to composition assets, identifies a relationship between two representations of an asset resource:
- The
viewId
, or composition view
, represents the composition asset that is embedded in a specific sound recording. The composition view is the canonical set of information that YouTube displays about the composition rights for a given recording and may synthesize information from multiple data providers. . - Each sound recording asset maps to exactly one
viewId
.
- Each
viewId
maps to one or more shareIds
. However, a viewId
only maps to multiple shareIds
when a composition has multiple owners. From a single content owner's perspective, a viewId
is associated with a single shareId
. This is because the content owner can only retrieve the shareIds
that represent data the content owner itself provided. Note that it's possible for a single content owner using the API to represent multiple owners of a composition and, therefore, own multiple shares of that composition. For example, an aggregator of digital rights could obtain rights to the same composition from different parties in different territories. The aggregator would have discrete entities representing those rights, which would map to different composition shares in YouTube's model. The different composition shares could still be linked to the same composition view(s).
- The
shareId
, or composition share, represents the information that a particular publisher provided for a composition asset. A shareId
can be associated with many sound recordings.
Many API methods enable you to retrieve or update information about an asset. The Managing composition assets
guide explains how those methods handle requests depending on whether the provided asset IDs are shareIds
or viewIds
.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-20 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[[["\u003cp\u003e\u003ccode\u003eAssetShare\u003c/code\u003e resources define the relationship between a composition's \u003ccode\u003eviewId\u003c/code\u003e (composition view) and \u003ccode\u003eshareId\u003c/code\u003e (composition share), relevant to composition assets.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003eviewId\u003c/code\u003e represents the composition asset embedded in a sound recording, and each sound recording maps to exactly one \u003ccode\u003eviewId\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003eshareId\u003c/code\u003e represents the information a publisher provides for a composition asset, and a \u003ccode\u003eviewId\u003c/code\u003e can map to one or more \u003ccode\u003eshareIds\u003c/code\u003e when a composition has multiple owners.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eAssetShare\u003c/code\u003e resource contains a \u003ccode\u003ekind\u003c/code\u003e, \u003ccode\u003eviewId\u003c/code\u003e, and \u003ccode\u003eshareId\u003c/code\u003e, where the \u003ccode\u003ekind\u003c/code\u003e is \u003ccode\u003eyoutubePartner#assetShare\u003c/code\u003e, the \u003ccode\u003eviewId\u003c/code\u003e is the unique asset view identifier, and the \u003ccode\u003eshareId\u003c/code\u003e is the unique asset share identifier.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eassetShares.list\u003c/code\u003e method enables retrieving asset shares associated with a \u003ccode\u003eviewId\u003c/code\u003e or asset views linked to a specific \u003ccode\u003eshareId\u003c/code\u003e owned by a partner.\u003c/p\u003e\n"]]],["The `assetShare` resource links composition views (`viewId`) and composition shares (`shareId`). A `viewId` represents a composition asset in a sound recording and can have multiple `shareIds` if a composition has multiple owners. A `shareId` represents a publisher's information for a composition and can be linked to many recordings. The API's `list` method retrieves either shares associated with a specific view or views associated with a specific share, owned by a content partner.\n"],null,["# REST Resource: assetShares\n\n- [Resource: AssetShare](#AssetShare)\n - [JSON representation](#AssetShare.SCHEMA_REPRESENTATION)\n- [Methods](#METHODS_SUMMARY)\n\nResource: AssetShare\n--------------------\n\nAn `assetShare` resource, which is only relevant to composition assets, identifies a relationship between two representations of an asset resource:\n\n- The `viewId`, or **composition view** , represents the composition asset that is embedded in a specific sound recording. The composition view is the canonical set of information that YouTube displays about the composition rights for a given recording and may synthesize information from multiple data providers. .\n - Each sound recording asset maps to exactly one `viewId`.\n - Each `viewId` maps to one or more `shareIds`. However, a `viewId` only maps to multiple `shareIds` when a composition has multiple owners. From a single content owner's perspective, a `viewId` is associated with a single `shareId`. This is because the content owner can only retrieve the `shareIds` that represent data the content owner itself provided.\n\n \u003cbr /\u003e\n\n Note that it's possible for a single content owner using the API to represent multiple owners of a composition and, therefore, own multiple shares of that composition. For example, an aggregator of digital rights could obtain rights to the same composition from different parties in different territories. The aggregator would have discrete entities representing those rights, which would map to different composition shares in YouTube's model. The different composition shares could still be linked to the same composition view(s).\n- The `shareId`, or **composition share** , represents the information that a particular publisher provided for a composition asset. A `shareId` can be associated with many sound recordings.\n\nMany API methods enable you to retrieve or update information about an asset. The [Managing composition assets](/youtube/partner/guides/managing_composition_assets) guide explains how those methods handle requests depending on whether the provided asset IDs are `shareIds` or `viewIds`.\n\n\u003cbr /\u003e\n\n| JSON representation |\n|-----------------------------------------------------------------|\n| ``` { \"kind\": string, \"viewId\": string, \"shareId\": string } ``` |\n\n| Fields ||\n|-----------|-----------------------------------------------------------------------------------------------------|\n| `kind` | `string` The type of the API resource. For this resource, the value is `youtubePartner#assetShare`. |\n| `viewId` | `string` A value that YouTube assigns and uses to uniquely identify the asset view. |\n| `shareId` | `string` A value that YouTube assigns and uses to uniquely identify the asset share. |\n\n| Methods ------- ||\n|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ### [list](/youtube/partner/reference/rest/v1/assetShares/list) | This method either retrieves a list of asset shares the partner owns and that map to a specified asset view ID *or* it retrieves a list of asset views associated with a specified asset share ID owned by the partner. |"]]
