Cannot use URI reserved character in API Query Profile parameters?

Matillion ETL
1

I am starting to add several more endpoints to one of my API Query profiles. When I attempt to send the request to test it, I get an error message that says "Invalid value: parameter <> contains a URI reserved character ("/" or "?")".

 

I know that this error is tied to one of my parameters but it's a parameter that I have successfully used before in this exact same Query Profile. My parameter is called 'Content-Type' and it has a value of 'application/json'. Needless to say, I'm at a loss as to why I am not able to use a / in my header values anymore when I could before.

 

Is anybody else seeing this or does anyone know of a way around it?

2

For anyone else having this issue, apparently it is a bug and will be fixed on the next release.

3

Hi @Austin​ facing the same issue!

Any idea on :

  1. When the bug will be fixed?
  2. Where do we get the bug fix version release details?
  3. API Extract profiler seems to work good. Any concerns in performance in using it over the Query profiler?

TIA for your help!