Maxime Broussard
11/25/2025, 11:17 PMkapa.ai
11/25/2025, 11:18 PMMaxime Broussard
11/25/2025, 11:20 PMMaxime Broussard
11/25/2025, 11:20 PMkapa.ai
11/25/2025, 11:20 PMkapa.ai
11/25/2025, 11:21 PMpage or page_number) and not an offset, you cannot use the Offset Increment strategy to increment the page number—Offset Increment is specifically for APIs that use an offset parameter, not a page number. The Offset Increment strategy injects an offset value (e.g., offset=0, offset=5, etc.), not a page number, into the request ([source](https://docs.airbyte.com/platform/next/connector-development/config-based/understanding-the-yaml-file/pagination#pagination-strategies)). The Page Increment strategy is designed for APIs that use a page number, but as you noted, it stops when a page returns fewer records than the page size, which is a limitation in your case ([source](https://docs.airbyte.com/platform/next/connector-development/config-based/understanding-the-yaml-file/pagination#pagination-strategies)). In summary: - You cannot use Offset Increment to increment a page number parameter. - If your API only supports page numbers, you are limited by the Page Increment strategy's default stop condition. - There is no configuration in the knowledge sources to change this stop condition. If you cannot change the API or use a different pagination indicator, the only alternative (not covered in the provided knowledge sources) would be to implement a custom pagination strategy, but this is not described in detail in the sources above. Conclusion: You cannot use Offset Increment to work around the Page Increment limitation for a page number parameter. The knowledge sources do not provide a solution for your scenario.