Clip Event Timestamp

The last time I checked the clip creation time (‘created_at’ key in Get Clip response) referred to when the clip was created and not when the clipped event occurred live.

For example if someone watched the stream and found an interesting event but waited until an hour later to clip it (from the VOD in this case), the creation time would refer to an hour after the event.

Would we be able to get a time of the event itself in the get clip response?

You mean the timeindex for the clip for the vod/.stream that is was clipped from? So for example you can go back to the vod and capture stuff before/after the clip?

You can take the clip slug that you got from Helix, and perform get clip against kraken

That has the information you are after.

compared to

Kraken/v5 just has more of the needed data

There are two separate timestamps I’m referring to.

  1. The created_at timestamp. The timestamp for when a user creates a clip. The created_at key in the Get Clip api call (for both of your links) refers to this.

  2. The live timestamp. A streamer will always perform live, and clips will always be created at some point after the event has occurred. This timestamp would refer to when the live event actually occurred, instead of when the clip was created, as in case 1.

I just clipped a segment from a VOD of a current livestream and went back 1 hour from live, the timestamp it gave in the created_at key was the time I clipped it (case 1). In this case, I would want a response that gave the created_at time minus 1 hour, the live timestamp.

Thanks for any responses.

Thats in the second link

"vod": {
"id": "340044952",
"url": "",
"offset": 14723,
"preview_image_url": ""

You can work it out by taking the offset and adding to the the get videos call for when the vod was created. It’s mathable, just not as a singular JSON key

VOD’s get deleted with some frequency, which disallows the above method in general.

Edit: Accidentally edited over this post.

Collect and store when the obtain the Clip details.

Other that that it’s just waiting to see if helix will include it before kraken v5 is removed

Okay thanks for fleshing out the options, sometimes there are some undocumented api endpoints that prove useful.

I’ll post this in the requested features forum.

For reference I’ve not cited any undocumenteds here. Just the v5 end point

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.