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

Airbyte

*Setup an Incremental and Inject as a request parameter*
I am confused on where to implement date incremental sync with parameters.
This is the OpenAPI endpoint :
<https://axonaut.com/api/v2/doc>
/api/v2/invoices

I was able to have full_sync with
```version: "0.1.0"

definitions:
  selector:
    extractor:
      field_pointer: []
  requester:
    url_base: "<https://axonaut.com/api/v2>"
    http_method: "GET"
    authenticator:
      type: ApiKeyAuthenticator
      header: "userApiKey"
      api_token: "{{ config['userApiKey'] }}"    
    request_options_provider:
      request_parameters:
        date_after: "{{ config['date_after'] }}"      
  stream_slicer:
    type: "DatetimeStreamSlicer"
    start_datetime:
      datetime: "{{ config['date_after'] }}"
      datetime_format: "%d/%m/%Y"
    end_datetime:
      datetime: "{{ now_utc() }}"
      datetime_format: "%Y-%m-%d %H:%M:%S.%f+00:00"
    step: "P1D"
    datetime_format: "%d/%m/%Y"
    cursor_field: "{{ options['stream_cursor_field'] }}"   
    cursor_granularity: "P1D"
  retriever:
    record_selector:
      $ref: "*ref(definitions.selector)"
    paginator:
      type: NoPagination
    requester:
      $ref: "*ref(definitions.requester)"
    stream_slicer:
      $ref: "*ref(definitions.stream_slicer)"      
  base_stream:
    retriever:
      $ref: "*ref(definitions.retriever)"
  invoices_stream:
    $ref: "*ref(definitions.base_stream)"
    $options:
      name: "invoices"
      primary_key: "id"
      path: "/invoices"
      request: ""
      stream_cursor_field: "date"

streams:
  - "*ref(definitions.invoices_stream)"

check:
  stream_names:
    - "invoices"

spec:
  documentation_url: <https://docs.airbyte.com/integrations/sources/axonaut>
  connection_specification:
    title: Axonaut Spec
    type: object
    required:
      - userApiKey
    additionalProperties: true
    properties:
      # 'TODO: This schema defines the configuration required for the source. This usually involves metadata such as database and/or authentication information.':
      userApiKey:
        type: string
        description: API access key used to retrieve data from the Exchange Rates API.
        airbyte_secret: true
      date_after:
        type: string
        description: Start getting data from that date.
        pattern: ^(0[1-9]|[12][0-9]|3[01])[- /.](0[1-9]|1[012])[- /.](19|20)\d\d$
        examples:
          - "%d/%m/%Y"```


Hi, Thomas! Just to make sure I understand - you are developing a custom connector for this API?

I mainly followed the exchangerates_data Low-code CDK tutorial which shows an exemple with *path*

<https://docs.airbyte.com/connector-development/config-based/tutorial/incremental-reads>

I am looking at _start_time_option_

```    start_time_option:
      field_name: "date_after"
      inject_into: "request_parameter"
    end_time_option:
      field_name: "date_before"
      inject_into: "request_parameter"  ```

Got it! Unfortunately right now our team does not have the staffing capacity to support custom connector development. I encourage you to reach out to community members that have developed custom connectors and ran into similar issues!