Partner API: best practices and asset requirements
Rules that keep API deliveries flowing: primaryArtist as an array, MP4 video up to 5 GB, 1280×720 or 1080p thumbnails, no watermarks, idempotent videoIds, and the content standards every video must meet.
The API validates structure, but ANS Music still reviews every video before it goes to platforms. Following these practices avoids both 400s and review rejections.
Request hygiene#
primaryArtistmust be an array — always, even for one artist.- Use stable, unique
videoIds from your own system. They make retries safe (a duplicate returns409rather than creating a second delivery). - One video per request. Batch on your side with a queue; don’t parallelise dozens of 5 GB uploads at once.
- Send the ISRC of the audio recording that’s in the video, matching the audio release if it exists — that’s how platforms link video and audio.
- Log the response for every call, including the body on errors.
Asset requirements#
| Asset | Requirement |
|---|---|
| Video | MP4, maximum 5 GB. Full HD (1920×1080) or higher, clean visuals and audio. |
| Thumbnail | JPG or PNG, 1280×720 or 1080p. A clean still from the video. |
| Watermarks | None. No logos, watermarks, social handles, URLs or contact information in the video or thumbnail. |
Content standards still apply#
API deliveries go through the same review as Backstage uploads. Anything in these categories is rejected regardless of a valid request:
- Promotional content — tour / event announcements, merch promos, countdowns, behind-the-scenes clips.
- Cover songs, remakes and interpolations of copyrighted works.
- AI-generated audio or video, in whole or in part — a material breach of the Video Distribution Agreement. See AI-generated content policy.
- Videos that fail VEVO’s production standard. Full list in VEVO video requirements.
A music video that hasn’t reached 100,000 views within 3 months of upload may be taken down as non-valuable content, without notice and without a fee. Plan promotion for each delivery, not just the upload.
Security#
- Store the API key in a secrets manager or environment variable; never in source control or client-side code.
- Restrict which servers can make outbound calls with the key.
- Rotate the key if anyone who had access leaves your team — ask us to issue a new one.
Thanks — your feedback helps us improve this article.
Still stuck?
Our support team answers tickets every business day. Include your account email and the release UPC or ISRC so we can jump straight in.