Skip to content
Translate Ideas and Comments
Choose language:
There was an error during translation
← Developers

How can we improve the developer experience on Twitch?

Developers: API

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Extend the Clips API to include recreation from source information

The clips API

https://dev.twitch.tv/docs/api/reference#get-clips

doesn't contain enough information to recreate the clip from the source video, it doesn't have the length of the clip or the start point in the vod.
38 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

BarryCarlyon shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Comments are closed An error occurred while saving the comment
  • Adminecressey (Admin, Twitch) commented  ·   ·  Report

    Hello Barry! We added the duration field to Get Clips pretty recently, so check it out if you missed it. We will take a look at vod_offset; I might have missed that the first time I looked at this.
  • AnD4D commented  ·   ·  Report

    Can this be a thing yet, please? I have a command that pulls up a Twitch clip, but I also have to limit it to 30 seconds because I have no duration.

    If the clip is longer than 30 seconds, it just stops mid-way through. If it's shorter than 30 seconds, I have to sit on a blank screen until 30 seconds pass or I manually end the clip.
  • csharpfritz commented  ·   ·  Report

    These fields would be VERY valuable to help present clips on another website or application in the correct order that the original content was created
  • Tenosis commented  ·   ·  Report

    I'm surprised that there's *still* no "video_offset" available in the new API. It's clearly not difficult to do since it's available in the v5 API and is used on the Twitch clip pages to go to the source video.
  • tastyfriedtofu commented  ·   ·  Report

    The clips api in helix endpoint lacks so many information. No integer IDs, no VOD timestamp, no duration, etc... I hope they released a fix for this before dropping v5 endpoint.

    Using slugs as ID is weird as other endpoints still use integer for their IDs.
  • RatWithAShotgun commented  ·   ·  Report

    needed clip info:

    * duration:
    like v5

    * vod_offset:
    like v5, to make timestamped vod links to the point of the clip

    * occured_at:
    there's created_at but that can be months or years off when the actual content in the clip happened if the clip was made from a VOD or highlight.
    occured_at can be calculate while the vod is still alive as vod.created_at + clip_v5.vod_offset but once the VOD is deleted there's no way to get that info anymore.

    needed for deduplication, searching for specific clips of an event, recreating from local recordings and much more.

    currently the started_at and endeded_at params for the clip API are using created_at, would be nice to also have ones to search by occured_at in addition

  • GenideGaming commented  ·   ·  Report

    What is more surprising is that duration and the vod information exists on the v5 get clips API (kraken), but not on the new get clips API (helix).