When configuring Digital Signage playlist display period for a Zoom Room using the Settings API, the playlist is being scheduled for the entire day, ignoring the specified display time window.
PATCH /v2/rooms/{roomId}/settings?setting_type=signage
Request body:
{
“digital_signage”: {
“layout”: “standard”,
“mute”: false,
“banner”: {
“banner_room_name”: true,
“banner_time”: true,
“banner_sharing_key”: true
},
“enable_digital_signage”: true,
“display_period”: {
“start_displaying_content”: 5,
“stop_displaying_content”: 5
},
“play_list”: [
{
“name”: “Tuesday”,
“action”: “add”,
“contents”: [
{
“duration”: 10,
“order”: 1,
“content_id”: “fs-6835FE1A4CBF179D72AADA164A54E79B”
}
],
“start_time”: “2026-02-10T13:00:00Z”,
“end_time”: “2026-02-10T17:00:00Z”
}
]
}
}
Some one pls help on this.
Hi @Surya.yadavalli , can you please share the response and the zm-tracking-id from the response header?
Hi @gianni.zoom
I tried with new request.
URL: PATCH https://api.zoom.us/v2/rooms/YJ1b6QjyjeteXs3_NDA/settings?setting_type=signage
request body :
{
"digital_signage": {
"layout": "standard",
"mute": false,
"banner": {
"banner_room_name": true,
"banner_time": true,
"banner_sharing_key": true
},
"enable_digital_signage": true,
"display_period": {
"start_displaying_content": 5,
"stop_displaying_content": 5
},
"play_list": [
{
"name": "Schedule Test",
"action": "add",
"contents": \[
{
"duration": 10,
"order": 1,
"content_id": "fs-6835FE1A4CBF179D72AADA164A54E79B"
}
],
"start_time": "2026-02-12T07:30:00Z",
"end_time": "2026-02-12T11:30:00Z"
}
\]
}
}
zm-tracking-id : v=2.0;clid=us06;rid=WEB_f930fe5a53f34a6b33c631bb768c5858
response : Empty response body with status 204
@gianni.zoom Can i get information for this issue, we have some production release soon. Thanks !!
Hi @Surya.yadavalli ,
I’ve reached out to the service engineering team about this API behavior (ZSEE-195126). Please note that the forum is for community help and we do not have an SLA, but I am following up often to try to help you 
If you’d like SLA support, please use the premier developer support option.
Hi @Surya.yadavalli ,
Here’s what our investigation found:
The issue is that you are using room_id instead of “id” field from GET /v2/rooms API. You should use the id field. room_id is only used for dashboard APIs. id field is the actual zoom room user id. They should copy the id value and use it for the settings API
If you use the correct id, then it shows correctly in web portal.
We know this is confusing, so the service engineering team has made an API enhancement request to address this.
Can you please test with the new parameter and let me know if it works?