@kapa.ai ?

For instance, I set

owner: (sponsoredAccount:urn%3Ali%3AsponsoredAccount%3A506989960)

, that leads to

owner=%28sponsoredAccount%3Aurn%253Ali%253AsponsoredAccount%253A506989960%29

in the final query => not accepted by LinkedIn API

I would like to keep

(

and

:

and

)

original values

@kapa.ai is it more clear ?

I'm sorry, but your question is still not clear. Could you please provide more details or context? I'm here to help with any questions related to Airbyte, an open-source data integration engine.

@kapa.ai Using the

UI Builder/low code

connector development, I am facing an issue regarding

query param

special characters auto-escaping. For instance, I set

owner: (sponsoredAccount:urn%3Ali%3AsponsoredAccount%3A506989960)

as query param, leading to

owner=%28sponsoredAccount%3Aurn%253Ali%253AsponsoredAccount%253A506989960%29

in the final query generated, which is not accepted by LinkedIn API. I would like to keep

(

and

:

and

)

original values. How can I force them not to be escaped in the YAML or UI builder?

Based on the information provided in the knowledge sources, it seems that Airbyte's low-code CDK (Connector Development Kit) automatically URL-encodes special characters in query parameters. This is to ensure that the URL is correctly formatted and can be properly interpreted by the server. However, there is an open issue on Airbyte's GitHub page ([#29918](https://github.com/airbytehq/airbyte/issues/29918)) discussing the need to URL-encode every special character in query parameter values. The issue suggests that the low-code CDK should URL-encode every special character in the input value, and set that whole URL-encoded string as the value on the query parameter. In the comments of the issue, there is a discussion about handling cases where the value of a query parameter has the structure of a list. The proposed logic is to treat it as a list and unpack it if it starts with

[

, ends with

]

, and the elements are comma-separated. Otherwise, the value is treated as a string and URL-encoded. Unfortunately, there doesn't seem to be a direct way to prevent specific characters from being URL-encoded in the current version of Airbyte's low-code CDK. You might want to follow the progress of the mentioned issue or contribute to the discussion on GitHub. For more complex cases where the API has special requirements that can't be handled by the "Inject Parameter / Parent Key Value into outgoing HTTP Request" option, the [Airbyte documentation](https://docs.airbyte.com/connector-development/connector-builder-ui/partitioning#custom-parameter-injection) suggests disabling injection in the component and using the generic parameter section at the bottom of the stream configuration form to freely configure query parameters, headers, and properties of the JSON body, by using jinja expressions and available variables. However, this might not solve your specific issue with URL encoding. Please note that this information is based on the provided knowledge sources and the current state of Airbyte's low-code CDK. The actual solution might vary depending on the specific requirements of the LinkedIn API and the capabilities of the CDK.