Add Pagination to the findRooms API, to get past the limit of 100 rooms
The /findRooms API states: "You can get up to the first 100 rooms in the tenant". Could you please add standard Pagination, to get past this limit?
I tried /findRooms?$top=1000&$count=true but I am not able to make these query parameters work. In addition, I now understand that the API doesn't currently support things like $top or $skip.
We are moving from the findRooms API to our new Places API. The Places API is available in BETA. We will be adding pagination to this API. Our target date to deliver this is end of January.
Document can be found here: https://docs.microsoft.com/en-us/graph/api/resources/place?view=graph-rest-beta
Iskandar Setiadi commented
Is there any workaround to this issue? It's almost 2 years since this issue was added
I wonder why this request is one of the most popular but the only one without any official status. Is it so complicated to remove this limitation?
Is this ever going to get fixed?
Alexander Soto commented
Also can't use this API properly without support for paging. Or even better adding paging and a query string option...
This API is basically useless without pagination. Any timeline for it being added?
Please add this.
Is there any workaround for this issue? It seems impossible to retrieve all rooms unless they're organized in room lists - which is not the case for many of my clients.
+1 to this. This is severely limiting the usefulness of the API and blocking our ability to use Office 365
Yes please, this is very needed.
Rick Knowler commented
This is really needed, please add
Mike O'Neil commented
Lack of pagination and accepting a filter parameter to filter the room name makes this API resource nearly unusable for any sizable company. This affects many of our customers. Would be great to get this prioritized eventually!
[Deleted User] commented
this and why don't we have a NextLink in the findRooms result ?
this API is inconsistant.