GET: /workspaces/-1fDbDtnQSa5FeMPXdTotA##WS
Object returned (changed location_id into xxx):
{
“id”: “-1fDbDtnQSa5FeMPXdTotA##WS ”,
“location_id”: “xxxxxxxxxxxxxxxxxxxxxx”,
“workspace_name”: “P60”,
“workspace_type”: “”
}
GET: /workspaces/-1fDbDtnQSa5FeMPXdTotA##WS /reservations
Object returned:
{
“code”: 1012,
“message”: “Room does not exist: -1fDbDtnQSa5FeMPXdTotA##WS .”
}
Hi @drijkeboer
Thanks for reaching out to us and welcome to the Zoom Developer Forum!
Are you still having this issue or have you been able to troubleshoot this on your end?
Please let me know so I can take a closer look
Hi Elisa,
No haven’t been able to solve it. Seems to be a bug in the Zoom API when getting reservation info of a workspace that is workspace_type “custom” .
Kind regards,
Daniëlle
Thanks @drijkeboer
I will send you a DM, please follow up there with more information
To update this thread, this is expected behavior and there is a Feature Request open for this issue
system
(system)
Closed
March 5, 2025, 2:56pm
6
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.