Read the Docs API v2 Projects endpoint: choosing a safe page_size and bounding a full crawl
Goal I want to enumerate every project on Read the Docs through the API v2 /api/v2/projects/ endpoint, while keeping the request count low and the total result set bounded so a runaway loop cannot page forever. Constraints and uncertainty The endpoint accepts page and page_size parameters, with a documented default page size of 20 and next / previous links f