Airbyte Data Source Configuration: Dynamic "Replication Start Date"

Hi all,

Is there a way to configure Airbyte data source’s “Replication Start Date” dynamically? E.g. replicate data for the past three days from current day.

I tried to use an external procedure and reset “Replication Start Date” manually, every day, through the AirBytes API, but wasn’t able to find the corresponding API request.

We are using the shopify connector.

Is the above functionality supported at all?

I am aware of incremental-replication and how it updates data, but in our use case we need to use full-replication

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Hey @dvamvakidis,

Could you give me an example of what you’re trying to do here? Also why would incremental-replication not be a suitable solution here?

Hi @sajarin ,

First of all thanks for the reply.

We are trying to load sales data from shopify into a Postgres DB. The sales data of interest correspond, e.g. to the last 3 days from current date, so if its Dec 12th we want to load sales data between 12th and 10th of Dec.

Up until now, the only way we have been able to do the above is to manually change the date in the “Replication Start Date” field of the connector’s settings, before a sync takes place. However this is not practical and we attempted to create a scheduled task to sync data, using the airbytes API. We have been able to trigger a sync through the Airbytes API, but not to change the “Replication Start Date” value.

Is there any way this could be done through the API?

Incremental Replication is not an option, since we want to retrieve all data from the past 3 days, regardless of whether that data has changed or not since the last sync.

Thanks in advance.

Hey @dvamvakidis,

Thanks for the response. Have you considered using the “Update Source” endpoint for our API and programmatically passing in new replication start dates?

I’m not sure if this would solve your issue but perhaps it’s worth investigating.

Hi @sajarin,

Thank you for the suggestion. Using the API endpoint suggested, i managed to solve the problem!

Just for future reference to anyone interested, it is important to use the documentation of your source’s schema, in order to set the connectionConfiguration field. (e.g. for me the documentation could be found at ‘’).

Hey @dvamvakidis,

Thanks for reporting back with your suggestion for making this work for other users. Happy to hear you were able to use our API for your use case. Feel free to post more questions here in the forums!