youtube as the platform value in post targets and put YouTube-specific
settings in the target’s platformSpecificData.
YouTube is video-only in Kavenio. Each YouTube target uploads exactly one
long-form video or Short, then optionally applies a thumbnail, playlist
insertion, and first comment.
YouTube Shorts use the normal resumable video upload flow. Send a qualifying
vertical or square video through a YouTube target. YouTube supports eligible
Shorts up to three minutes and determines classification from the uploaded
video; there is no separate YouTube Shorts upload endpoint.
In Kavenio’s web composer, Publish as YouTube Short appends #Shorts to the
published description. That preference does not force YouTube to categorize the
upload as a Short—the video must still meet YouTube’s current eligibility rules.
Quick Reference
Create A Video Post
platformPostId and returns a native watch URL.
Required Fields
Kavenio validates YouTube targets before provider upload.
If both
platformSpecificData.thumbnailUrl and the video media item’s
thumbnail are present, Kavenio uses thumbnailUrl.
Platform-Specific Fields
Media URLs
YouTube pulls video and thumbnail bytes from your supplied URLs during publish. Video requirements:- The URL must be public and reachable when Kavenio publishes.
- Private, loopback, and localhost URLs are rejected.
- The response must return a non-empty body.
- The response content type must be
video/*orapplication/octet-stream.
- Use JPEG or PNG content.
- The response must return a non-empty body.
- The file must be 2 MB or smaller.
Thumbnails, Playlists, And First Comments
Kavenio performs post-upload follow-up actions in this order:- Upload the video.
- Upload a custom thumbnail, when one is supplied.
- Add the video to
playlistId, when one is supplied. - Add
firstComment, when one is supplied.
firstComment because YouTube does not make
comments available on private videos.
If a follow-up action fails after the video upload succeeds, Kavenio includes
partial raw provider data for the video and any completed follow-up actions in
the target failure details. Retrying reuses that video ID and resumes unfinished
follow-up actions instead of uploading a duplicate.
Kavenio does not mark the target published immediately after YouTube accepts the
upload. The worker polls YouTube processing status and publishes the final
Kavenio lifecycle event only after processing succeeds. Provider failure and
rejection reasons are recorded on a failed target.
First comments require a connected YouTube credential with the
youtube.force-ssl scope. If that scope is missing, Kavenio rejects the target
before upload.
Shorts
publishAsShort adds #Shorts to the description. It does not force YouTube to
classify a video as a Short. YouTube currently classifies eligible square or
vertical videos up to three minutes according to its own rules.
Provider Project Readiness
Uploads from unverified API projects created after July 28, 2020 are restricted to private viewing until the project passes YouTube’s compliance audit.videos.insert is currently limited to 100 calls per day in the Video Uploads
quota bucket, so live test plans should budget upload attempts and avoid using
retries as duplicate uploads.
Scheduling
Use Kavenio’s normal scheduling fields:Edit Published Videos
YouTube supports Kavenio’s published edit lifecycle for metadata updates.- title
- description through
content - tags
- category
- made-for-kids setting
- synthetic-media setting
- visibility
Unpublish Published Videos
YouTube unpublish changes the uploaded video’s visibility toprivate.
youtube.force-ssl.
Unsupported Cases
Kavenio does not support these YouTube actions through post publishing:- image-only posts
- text-only posts
- Community posts
- live streams or Premieres
- replacing an already-uploaded video file
- editing thumbnails after initial upload
- creating or deleting playlists
- uploading captions or subtitles
- managing monetization settings