Hi team, Getting this error while extracting Aircall call's data..

'GET' request to '<https://api.aircall.io/v1/calls?page=201&per_page=50>' failed with status code '400' and error message: 'BAD_REQUEST'. Request (body): 'None'. Response (body): '{'error': 'Bad Request', 'data': None, 'message': 'BAD_REQUEST', 'errors': 'Your query is limited to 10k results and pagination is out of bound, please use timestamps or other filters.', 'troubleshoot': 'BAD_REQUEST', 'success': False}'.

Have already defined

from_date

in the source definition but not sure what's going wrong ?

NAME    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                
airbyte airbyte         1               2026-04-05 17:06:51.975954 +0530 IST    deployed        airbyte-1.9.2

Airbyte version in Docker image:

airbyte/server:2.0.1

Hi Prakash, thanks for reporting this. The issue seems to be that the

calls

stream in the Aircall connector doesn't currently have date-based slicing (incremental sync) configured. The

numbers

and

teams

streams do have this, but

calls

was missed. What this means is that even though you've set

start_date

in your source config, the

calls

stream doesn't actually use it. Instead, it tries to paginate through all calls without any timestamp filters. Once you exceed 10,000 results, the Aircall API rejects the request because it enforces a 10k pagination limit and expects you to use `from`/`to` timestamp filters to narrow results. Unfortunately there's no workaround on the user side for this right now. Could you raise a GitHub issue/PR for this at https://github.com/airbytehq/airbyte/issues so it can be tracked and prioritized? You can reference that the

calls

stream in

source-aircall/manifest.yaml

needs an

incremental_sync

block similar to the

numbers

and

teams

streams.

Hi @Mark Grivnin, Thanks for the information. I have created the issue here.