These features are only available to partners using YouTube's Content Manager to manage their copyrighted content.
Learn how to submit a Takedown request for content you own on YouTube. A Content ID takedown request for a Sound Recording will cause deactivation of any active references provided by you, unless there are other owners on the asset and no other active references.
Takedowns from YouTube and YouTube Content ID
- To take down a Sound Recording from Content ID, send a Single Resource Release feed or an Audio Album feed with YouTube_ContentID as one of the MessageRecipients.
- To take down an album from YouTube, send an Audio Album feed with YouTube as one of the MessageRecipients.
To account for time zone differences, we recommend delivering an updated deal with an <EndDate>
set at least two days in the past. Deliver your terms following the same method used to deliver your original Sound Recordings.
The following code will result in an immediate global Takedown:
<DealList>
<ReleaseDeal>
<DealReleaseReference>R1</DealReleaseReference>
<Deal>
<DealTerms>
<TerritoryCode>Worldwide</TerritoryCode>
<ValidityPeriod>
<EndDate>2016-05-31</EndDate> <!-New syntax, end date specified..-->
</ValidityPeriod>
</DealTerms>
</Deal>
</ReleaseDeal>
</DealList>
You can also use this code to submit a Takedown request if using the<TakeDown>
tag:
<DealList>
<ReleaseDeal>
<DealReleaseReference>R1</DealReleaseReference>
<Deal>
<DealTerms>
<TakeDown>true</TakeDown> <!-- Old syntax, explicit takedown. -->
<TerritoryCode>Worldwide</TerritoryCode>
<ValidityPeriod>
<StartDate>2010-05-18</StartDate>
</ValidityPeriod>
</DealTerms>
</Deal>
</ReleaseDeal>
</DealList>
If you’re submitting a Takedown request for Content ID, all <SoundRecordingDetailsByTerritory>
elements in the feed must have a <RightSharePercentage>
of zero:
<SoundRecordingDetailsByTerritory>
<TerritoryCode>ZA</TerritoryCode>
[...]
<RightsController>
<PartyId>PADPIDAZZZZXXXXXXU</PartyId>
<PartyName>
<FullName>ABC Label</FullName>
</PartyName>
<RightsControllerRole>RightsController</RightsControllerRole>
<RightSharePercentage>0.00</RightSharePercentage>
<RightsControllerType>RightsOwner</RightsControllerType>
</RightsController>
[...]
</SoundRecordingDetailsByTerritory>
Ownership will be removed in all omitted territories, so there’s no need to include all previously-delivered territories in your request
Deactivate Creator Music license strategies
To take down a Sound Recording from Creator Music only, send a Single Resource Release feed or an Audio Album feed with YouTube_CreatorMusic as the only MessageRecipient.
To deactivate all Creator Music license strategies for a given track, send a takedown request with YouTube_CreatorMusic as the only MessageRecipient. This will not impact your YouTube Premium and YouTube Content ID settings. Omit <DealList>
to indicate that existing license strategies on the delivered Sound Recordings should be deactivated.
<MessageHeader>
<MessageSender>
<PartyId>PADPIDAZZZZXXXXXXU</PartyId>
<PartyName>
<FullName>ABC Label</FullName>
</PartyName>
</MessageSender>
<MessageRecipient>
<PartyId>PADPIDA2022021109P</PartyId>
<PartyName>
<FullName>YouTube_CreatorMusic</FullName>
</PartyName>
</MessageRecipient>
</MessageHeader>
[...]
<DealList/>
If a sound recording has a platform and channel strategy, but you’d like to deactivate one:
- Send a feed with YouTube_CreatorMusic as the only MessageRecipient.
- Deliver the license strategy you’d like to remain active and omit the strategy you’d like to deactivate.
Combined feed Takedowns: YouTube Premium, Content ID, and Creator Music
To take down a Sound Recording from YouTube, Content ID, and Creator Music, send an Audio Album feed with all three MessageRecipients: YouTube, YouTube_ContentID, and YouTube_CreatorMusic.
To take down a Sound Recording from YouTube, Content ID, and Creator Music, send a feed that contains all three MessageRecipients. Omit the <DealList>
to indicate that the content should be taken down from YouTube and Content ID, and all Creator Music license strategies should be deactivated for the Sound Recording.
<MessageHeader>
<MessageId>20170112112123022</MessageId>
<MessageSender>
<PartyId>DPID_OF_THE_SENDER</PartyId>
<PartyName>
<FullName>Test Label</FullName>
</PartyName>
</MessageSender>
<MessageRecipient>
<PartyId>PADPIDA2013020802I</PartyId>
<PartyName>
<FullName>YouTube</FullName>
</PartyName>
</MessageRecipient>
<MessageRecipient>
<PartyId>PADPIDA2015120100H</PartyId>
<PartyName>
<FullName>YouTube_ContentID</FullName>
</PartyName>
</MessageRecipient>
<MessageRecipient>
<PartyId>PADPIDA2022021109P</PartyId>
<PartyName>
<FullName>YouTube_CreatorMusic</FullName>
</PartyName>
</MessageRecipient>
<MessageCreatedDateTime>2017-01-09T22:59:41.662+01:00</MessageCreatedDateTime>
<MessageControlType>LiveMessage</MessageControlType>
</MessageHeader>
[...]
<DealList/>
You can prepare a YouTube and Content ID takedown feed using either the <Takedown>
tag or an updated deal with an <EndDate>
set at least two days in the past and add in the YouTube_CreatorMusic MessageRecipient.
Example 1: The XML below shows a takedown request using the <Takedown>
tag:
<MessageHeader>
<MessageId>20170112112123022</MessageId>
<MessageSender>
<PartyId>DPID_OF_THE_SENDER</PartyId>
<PartyName>
<FullName>Test Label</FullName>
</PartyName>
</MessageSender>
<MessageRecipient>
<PartyId>PADPIDA2013020802I</PartyId>
<PartyName>
<FullName>YouTube</FullName>
</PartyName>
</MessageRecipient>
<MessageRecipient>
<PartyId>PADPIDA2015120100H</PartyId>
<PartyName>
<FullName>YouTube_ContentID</FullName>
</PartyName>
</MessageRecipient>
<MessageRecipient>
<PartyId>PADPIDA2022021109P</PartyId>
<PartyName>
<FullName>YouTube_CreatorMusic</FullName>
</PartyName>
</MessageRecipient>
<MessageCreatedDateTime>2017-01-09T22:59:41.662+01:00</MessageCreatedDateTime>
<MessageControlType>LiveMessage</MessageControlType>
</MessageHeader>
[...]
<DealList>
<ReleaseDeal>
<DealReleaseReference>R1</DealReleaseReference>
<Deal>
<DealTerms>
<TakeDown>true</TakeDown>
<TerritoryCode>Worldwide</TerritoryCode>
<ValidityPeriod>
<StartDate>2017-01-12</StartDate>
</ValidityPeriod>
</DealTerms>
</Deal>
</ReleaseDeal>
</DealList>
Example 2: Below you’ll find a combined takedown feed that uses the <EndDate>
method:
<MessageHeader>
<MessageId>20170112112123022</MessageId>
<MessageSender>
<PartyId>DPID_OF_THE_SENDER</PartyId>
<PartyName>
<FullName>Test Label</FullName>
</PartyName>
</MessageSender>
<MessageRecipient>
<PartyId>PADPIDA2013020802I</PartyId>
<PartyName>
<FullName>YouTube</FullName>
</PartyName>
</MessageRecipient>
<MessageRecipient>
<PartyId>PADPIDA2015120100H</PartyId>
<PartyName>
<FullName>YouTube_ContentID</FullName>
</PartyName>
</MessageRecipient>
<MessageRecipient>
<PartyId>PADPIDA2022021109P</PartyId>
<PartyName>
<FullName>YouTube_CreatorMusic</FullName>
</PartyName>
</MessageRecipient>
<MessageCreatedDateTime>2017-01-09T22:59:41.662+01:00</MessageCreatedDateTime>
<MessageControlType>LiveMessage</MessageControlType>
</MessageHeader>
[...]
<DealList>
<ReleaseDeal>
<DealReleaseReference>R1</DealReleaseReference>
<!-- This Deal is for YouTube Premium.-->
<Deal>
<DealTerms>
<CommercialModelType>AdvertisementSupportedModel</CommercialModelType>
<CommercialModelType>SubscriptionModel</CommercialModelType>
<Usage>
<UseType>OnDemandStream</UseType>
</Usage>
<TerritoryCode>Worldwide</TerritoryCode>
<ValidityPeriod>
<!-- For a takedown, the EndDate should be set in the past -->
<EndDate>2017-01-12</EndDate>
</ValidityPeriod>
</DealTerms>
</Deal>
<!-- This deal is for Content ID-->
<Deal>
<DealTerms>
<CommercialModelType>RightsClaimModel</CommercialModelType>
<Usage>
<UseType>UserMakeAvailableLabelProvided</UseType>
<UseType>UserMakeAvailableUserProvided</UseType>
</Usage>
<TerritoryCode>Worldwide</TerritoryCode>
<ValidityPeriod>
<!-- For a takedown, the EndDate should be set in the past -->
<EndDate>2017-01-12</EndDate>
</ValidityPeriod>
<RightsClaimPolicy>
<RightsClaimPolicyType>Monetize</RightsClaimPolicyType>
</RightsClaimPolicy>
</DealTerms>
</Deal>
</ReleaseDeal>
</DealList>
Was this helpful?
How can we improve it?