Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

I'm creating a custom *Rest API* connector using *UI builder tool*.

I have question regrading *incremental sync* support. Is it possible to generate a more sophisticated JSON payload using *incremental sync form*?

Sample filter criteria that needs to be passed to the API - and last sync date needs to be injected here as well:
`{`
  `"filterCriteria": [`
    `{`
        `"field": "lastModifiedDate",`
        `"operator": "AFTER",`
        `"value": "2023-04-02"`
    `}`
  `],`
  `"sortingCriteria": {`
    `"field": "lastModifiedDate",`
    `"order": "ASC"`
  `}`
`}`

Hi Vladimir, this is on our roadmap, and I added your example on <https://github.com/airbytehq/airbyte/issues/18784|the issue> as an additional use case to support, but I don't have an ETA on this feature yet

Thanks for the info.

Is there a way to get around this until it's implemented?

This is the part of the manifest generated by the connector builder:

```incremental_sync:
  type: DatetimeBasedCursor```
I was wondering if there is a way to implement custom class (and inject implementation instead of DatetimeBasedCursor) that would send JSON payload?