get the next available results from the REST API query

Pagination is not supported.  You can increase the maximum returned here, within reason: Searching using the M-Files Web Service (REST API)

Thanks!

When reading this I understand that I should pass the limit=5000 if I want maximum 5000 objects and limit=20000 if I want 20000 objects?

https://m-files-server.com/REST/objects?o=102&p1185=2&limit=20000

Yes, but note the comment at the bottom; you cannot continue to increase that value ad infinitum.

Hi, I tried to work around the limits by using a view created in M-Files. The view contains about 300 items, but it seems like getting objects from a view is limited to a maximum of 200 items. I cannot apply the limit parameter to views?

The two endpoints are different; you cannot increase the value like that for a view listing, only a search.  The size of data returned from views is controlled by the vault itself, inside the advanced vault settings I seem to recall.

You could, of course, create a view with some sort of grouping that breaks the object data into page-size chunks, then retrieve the root content of the view (to get the groups), then iterate through each grouping and return data from each one in turn.

For simple processes though I would revert back to the search and increase the limit.

The two endpoints are different; you cannot increase the value like that for a view listing, only a search.  The size of data returned from views is controlled by the vault itself, inside the advanced vault settings I seem to recall.

You could, of course, create a view with some sort of grouping that breaks the object data into page-size chunks, then retrieve the root content of the view (to get the groups), then iterate through each grouping and return data from each one in turn.

For simple processes though I would revert back to the search and increase the limit.

I encountered a problem accessing the virtual folders made by grouping. I get an error. Is it the syntax i have wrong when accessing a virtual folder? Should I use V{Virtual folder ID} or another letter?

I understand that the documentation on the encoding syntax can be awkward.  Maybe take a look at the MFWSClient sample library which has a "GetPath" extension method which does all the encoding?

https://github.com/M-Files/Libraries.MFWSClient/blob/0f068c58d88219cd51c9cd9535ae1998888715b5/MFaaP.MFWSClient/ExtensionMethods/FolderContentItemExtensionMethods.cs#L73