Open Emilgardis opened 12 months ago
Same issue is present in docs for Snooze Next Ad
and channel.ad_break.begin
also exhibits the same behavior in the docs, is_automatic
is also a string "false"
in the example
Also the dates received do not match the format specified in the documentation.
Doc says it's an RFC3339 format (and the json example show "2023-08-01T23:08:18+00:00") but we get a number timestamp in seconds for snooze_refresh_at
, next_ad_at
and last_ad_at
.
The endpoints are now GA, but the issue persists for the examples, the documentation still says they are integers, but example uses strings.
length_seconds
-> duration
preroll_free_time_seconds
-> preroll_free_time
it also still returns
{
"data": [
{
"duration": 0,
"last_ad_at": 0,
"next_ad_at": 0,
"preroll_free_time": 0,
"snooze_count": 0,
"snooze_refresh_at": 0
}
]
}
on unaffiliated channels
length_seconds
-> duration
snooze_count
Brief description
Get Ad Schedule documents
length_seconds
,preroll_free_time_seconds
andsnooze_count
as integers, while the example shows strings.Expected documentation
Additional context or questions
The endpoint doesn't specify what happens if it's used on a channel without ads-manager. I get the output
i'd expect it to give me a 404 or no data
-- https://github.com/twitchdev/issues/issues/857#issuecomment-1800822567
snooze_refresh_at
,next_ad_at
andlast_ad_at
return integers in a real payload