Hello @flarco I'm writing an API Spec with dynamic endpoints, and I'm trying to use a state variable to construct the jmsepath/jq expression inside the

response.records

map. However I'm getting an error when running the replication. It seems like it is not injecting the state variable before passing the expression to jmsepath.

# Excerpt from spec.yaml

defaults:
  state:
    url: 'https://api.lightspeedapp.com/API/V3/Account/{inputs.account_id}/{state.endpoint_name}.json'
  request:
    url: '{state.url}'

dynamic_endpoints:
  - iterate: '["Employee","CustomerType"]'
    into: 'state.endpoint_name'
    endpoint:
      name: '{snake(state.endpoint_name)}'
      response:
        records:
          jmespath: '{state.endpoint_name}[]'
          primary_key: '{snake(state.endpoint_name)}_id'
        processors:
          - expression: 'object_casing(record, "snake")'
            output: 'record'

The error message:

3:19PM INF execution failed

~ could not perform request
could not evaluate jmespath "{state.endpoint_name}[]" => SyntaxError: Expected tColon, received: tDot

context canceled

hey @mariovw, that's an interesting approach, currently the value in jmespath/jq doesn't render expressions/variables (they only accept raw strings). That's a nice feature, let me see if we can add for next release.

Thanks @flarco, for now I found a workaround, but let me know if you include it in a release so I can update the spec to make it more robust for my use case. Also, can API Specs be defined using Python?

Yes, already done for next release. For API Spec via Python, not possible currently. Let me consider this.

Great, thanks! Will be on the lookout for the next release. I was asking for API Spec via Python to know if it was currently possible, as it would have been another way of achieving the dynamic endpoint. But with the change you already did then I would not need API Spec via Python for now.

@mariovw yes you're correct, there was a piece missing in the implementation. Should be good now, is tested. you can use the [dev build](https://github.com/slingdata-io/sling-cli?tab=readme-ov-file#automated-dev-builds) if you'd like.