In a custom connector in Airbyte cloud, I need to provide an end date for an API pull. how to get today’s date dynamically?

In Airbyte, the

end_date

for an API pull is typically set to today's date by default if not provided. This is mentioned in the [Amazon Seller Partner source setup guide](https://docs.airbyte.com/integrations/sources/amazon-seller-partner#step-2-set-up-the-source-connector-in-airbyte). However, if you're developing a custom connector and need to get today's date dynamically, you would need to implement this in your connector's code. The specific implementation would depend on the programming language you're using to develop the connector. Please note that not all APIs or connectors support an

end_date

parameter. If you're working with a specific connector and need this feature, you may need to request it specifically for that connector, as mentioned in the [Github Issue](https://github.com/airbytehq/airbyte/issues/12466) discussion. If you're developing a connector with Python, you might find the [stream slices example](https://discuss.airbyte.io/t/1710) useful, which is a method for handling date ranges in data extraction.

@kapa.ai start_date and end_date are required in the API endpoint

In many of Airbyte's connectors,

start_date

and

end_date

are indeed required fields. These fields are used to specify the time range for the data you want to extract from the source. For example, in the Facebook Marketing source, both

start_date

and

end_date

are required fields. The

start_date

and

end_date

should match the regex pattern

^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$

, which represents a date-time format. If the

end_date

is not set, it will result in always syncing the latest data. The same applies to the

start_date

in the CommerceTools source, where it is a required field [source](https://github.com/airbytehq/airbyte/issues/34133). However, there is an open issue on GitHub suggesting that

start_date

should be an optional field on all connectors. The idea is to reduce the number of inputs required from users, thereby increasing activation rates. If

start_date

is not input, the suggestion is to either use a default

start_date

or load all the data in the user's account [source](https://github.com/airbytehq/airbyte/issues/20412). Please note that the requirement of these fields may vary depending on the specific connector. Always refer to the documentation or the JSON schema of the specific connector for the most accurate information.

@kapa.ai I’m refering to implementing a custom connector in the Builder in Airbyte Cloud

A message from kapa.ai

@kapa.ai any chance doing this with Jinja in the YAML ? Like {{ time.now }}

A message from kapa.ai