Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Requirements for our own metadata (not sourced from Spotify)

Requirements for our own metadata (not sourced from Spotify)

Hello,

 

I have been developing a website for a small publisher, and it only uses Spotify's Web API for the ability to pre-save upcoming releases. The first quota extension request was denied because

  • "Metadata, cover art and audio content must be accompanied by a Spotify logo and a link back to the applicable artist, album, track, or playlist on the Spotify Service (Design Guidelines)"

This seems to relate to the "Attribution" and "Linking to Spotify" sections of the Design Guidelines, which state in their "When does this apply?" sections:

  • "If you use any Spotify metadata [...] it must always be accompanied by the Spotify brand."
  • "If you use any Spotify metadata [...] it must always link back to the Spotify Service."

However, all of the metadata—track, album, artist, cover art—on this site is owned and provided by us (specifically the publisher); none of it is collected from Spotify.

 

Therefore I would like you to clarify whether these requirements are actually intended to apply to metadata not sourced from Spotify (although the same information is available on Spotify, and so may be considered "Spotify Content" under the Developer Terms definition—I am not a lawyer and won't speculate further on whether the legalese is relevant).

Reply
0 Replies

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random