Those clip ids work in the new API but the problem is that V5 doesn’t accept those:
curl $AUTH -s 'https://api.twitch.tv/kraken/clips/BreakableAggressiveDumplingsRaccAttack-DjiASkxJm-XUDda_' | jq .
{
"error": "Bad Request",
"status": 400,
"message": "The parameter \"slug\" was malformed: the value must match the regular expression /^[a-zA-Z0-9]+[-]?[a-zA-Z0-9]+$/"
}
V5 is the only API that has the vod offset field. Helix is still missing that so currently it’s impossible to get the vod offset for clips with those formats.
Anyone know if the clip name format change was intentional, and if so if there’s any chance on V5 getting a quick fix to allow slugs with _ chars? Or preferably Helix just getting the vod_offset field?
Just waiting on Twitch to accept or reject the uservoice you already linked.
Yeah thats not a valid slug, so somethings awry somewhere. A weird front end bug. (Not third party) Potentially related to the weirdness with the clips service outage from the other day
Yeah definitely related to that outage, the first appearances of those new slug formats was about 3 mins before the outage where everything returned error 500 for almost an hour.
Initially I just assumed bug for those too but now that I saw new ones with that format appearing again just hours ago I was curious if that may actually be an intentional change in slug format for the future, especially since name generation would seem like an unlikely thing to randomly bug out that way.
. Thank you!!!