There is no way for me. to get all of my data through a single API call.

Typically REST APis have mechanisms for paging through API results.

But the documentation for the API I am using:

Has no mention of paging methods. Looking up other APIs indicates paging methods that do not appear to work on the Desk API.

It is. unacceptable that any modern API documentation does not cover this topic clearly, using the multiple different keywords (including paging, or "getting more results" etc) that make it easy to find.

Please take the time to fix ALL of your API documentation with information about how to properly page through results. This is a basic and non-obvious topic. all permutations of paging through results should be clearly covered.

I should not have to reverse engineer this by doing searches in github, which is what I am doing now.

To be perfectly frank, it is frightening to see this topic not covered. What else has your API team ignored? What other major features are not covered by documentation or forum posts? How could your API development team have missed this while doing play testing as they actually watched other people trying to implement their API in meaningful ways? Is it more likely that your API team is not play testing the use of. the API? Is this a mature APi? Is it safe for me to use a product that does not have a mature API?

For all of these questions the clarity of your response will be telling. I want to know how to page, and I want to know how you are going to fix the documentation and I want to know how your are going to fix a process that resulted in basic API functionality not being covered in documentation.

-Fred Trotter