Kevin Robert
12/03/2025, 3:48 PMkapa.ai
12/03/2025, 3:49 PMBAD_REQUEST from the Aircall API at a high page number usually means the pagination request is outside what the API accepts (for example, requesting a page that doesn’t exist or violating some paging rule). The error is coming directly from: GET <https://api.aircall.io/v1/contacts?page=201&per_page=50> The Aircall connector uses page-based pagination with page and per_page parameters against the v1 API.[\[Aircall source docs\]](https://docs.airbyte.com/integrations/sources/aircall) Given the information in the knowledge sources, there is no specific, documented Aircall bug for 400s at higher pages, and there are no connector-specific limits mentioned.[\[Aircall source docs\]](https://docs.airbyte.com/integrations/sources/aircall) The general pagination troubleshooting guidance is to: - Confirm the pagination method matches the API’s expectations. - Check for API limits on pages/records. - Verify parameters are being injected correctly.[\[Pagination troubleshooting\]](https://docs.airbyte.com/platform/next/connector-development/connector-builder-ui/pagination#troubleshooting) Since the docs don’t specify an exact max page or a known issue for Aircall, I can’t say definitively why page 201 fails. The most likely causes, based on the general guidance, are: 1. You’ve paged past what the API allows (max page or record limit). 2. The API is rejecting that page combination, returning 400 instead of an empty page. Concrete steps you can take: 1. Test the same request outside Airbyte Run the failing URL with curl or Postman using your Aircall credentials. If it still returns 400, it confirms an Aircall API limit/behavior rather than an Airbyte bug. 2. Try lower page numbers Manually test a few pages (e.g. page=150, page=180, page=200). If only higher pages fail, you’re likely hitting an Aircall-side limit. 3. Reduce page size Try per_page=25 (via Airbyte connector configuration only if/when that becomes configurable, or through a custom connector in the Connector Builder using Page Increment pagination). General best practice is to use the largest allowed page size, but some APIs behave differently at high pages.[\[Page Increment docs\]](https://docs.airbyte.com/platform/next/connector-development/connector-builder-ui/pagination#page-increment) 4. If you’re building a custom connector - Ensure you’re using Page Increment mode with page and per_page injected as request parameters.[\[Page Increment docs\]](https://docs.airbyte.com/platform/next/connector-development/connector-builder-ui/pagination#page-increment) - If needed, add a stop condition (e.g., stop when the API starts returning errors or empty data) as suggested in the pagination troubleshooting docs.[\[Pagination troubleshooting\]](https://docs.airbyte.com/platform/next/connector-development/connector-builder-ui/pagination#troubleshooting) Because the provided sources don’t include Aircall-specific maximum page/limit rules or a matching GitHub issue, I’m not able to give a definitive root cause beyond “the Aircall API is rejecting that page request.” If you confirm the 400 via direct API calls, the next step would be to: - Open an issue with Airbyte including logs and the exact request, and/or - Check Aircall’s official API docs/support for any documented paging limits.