Get Ad Schedule

QualiTTV · October 13, 2024, 10:04pm

next_ad_at
String
The UTC timestamp of the broadcaster’s next scheduled ad, in RFC3339 format. Empty if the channel has no ad scheduled or is not live.

The timestamp I receive is not in RFC3339 format. I receive a unix timestamp like 1728825458 instead. Please also check the fields last_ad_at and snooze_refresh_at. Thank you!

BarryCarlyon · October 13, 2024, 10:05pm

documentation is incorrect pending a fix to the documentation

github.com/twitchdev/issues

Get Ad Schedule - `length_seconds`, `preroll_free_time_seconds` and `snooze_count` documented integers but example uses strings

opened 02:59PM - 05 Nov 23 UTC

Emilgardis

product: docs

**Brief description** Get Ad Schedule documents `length_seconds`, `preroll_fr…ee_time_seconds` and `snooze_count` as integers, while the example shows strings. **Expected documentation** ```json { "data": [ { "next_ad_at" : "2023-08-01T23:08:18+00:00", "last_ad_at" : "2023-08-01T23:08:18+00:00", "length_seconds" : 60, "preroll_free_time_seconds" : 90, "snooze_count" : 1, "snooze_refresh_at" : "2023-08-01T23:08:18+00:00", }, ], } ``` **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 ```json { "data": [ { "snooze_count": 0, "snooze_refresh_at": 0, "next_ad_at": 0, "length_seconds": 0, "last_ad_at": 0, "preroll_free_time_seconds": 0 } ] } ``` 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` and `last_ad_at` return integers in a real payload

QualiTTV · October 13, 2024, 10:15pm

Maybe it’s not the documentation that should be fixed here. Other API endpoints do indeed return timestamps in RFC3339 format. Would be nice if it would be consistent.

#961 describes exactly my issue and is NOT a duplicate of #857

BarryCarlyon · October 13, 2024, 10:18pm

They can’t change an API thats in general use by everyone as these endpoints are GA/General Availability.

as everyone at this point is expecting unix timestamps

Hence 961 was closed.

So I don’t think or expect them to change the API here

QualiTTV · October 13, 2024, 10:26pm

I don’t know how much this endpoint is really used but I do understand. Still - the two issues are not really duplicates. One is about some fields having the wrong type. The other one is about other fields (of the same endpoint) delivering the wrong format. Even if only the documentation can be changed, then the two issues still talk about different fields that need fixing in the documentation.

Appreciate the quick replies. Thank you very much. I’ll rely on the unix timestamps in this endpoint then (which is weird because inconsistent) but I can live with it.

QualiTTV · October 14, 2024, 8:14am

This part is also not correct:

Empty if the channel has no ad scheduled or is not live.

For next_ad_at we do receive a timestamp if the channel is not live. We shouldn’t.

system · November 13, 2024, 8:15am

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