Repository navigation
Query parameters not properly URL-encoded (pandas data pipeline) #9
Description
Activity
I think the root cause here might be related to the
client.requestmethod, which is using theparamsdictionary directly without URL-encoding the query parameters. IIRC, therequestslibrary (which is likely being used under the hood) expects the query parameters to be passed as adictwith the keys being the parameter names and the values being the parameter values. However, it does not automatically URL-encode the values. You might want to try using theurllib.parse.urlencodefunction to encode theparamsdictionary before passing it to theclient.requestmethod.Reacted by Francesco Bianco (yafb)Good point, thanks @IlyasFardaouix for looking into it.
We’re currently experimenting with a slightly different approach using Pandas for handling responses, so this area is still evolving on our side.
Any suggestions or experiments around improving the decoding/handling flow are more than welcome — feel free to share ideas or even open follow-up PRs.
Reacted by Ilyas Fardaoui- added a commit that references this issue
on Apr 14, 2026 Great work @Deadpool2000, thanks for the PR! 🙌
Even though this seems to fix the issue, we’ll keep it open for now so we can run some internal tests in our environment over the next few months.
Once everything is fully verified and confirmed as stable, we’ll proceed with closing the issue.
Thanks again for your collaboration!
Reacted by Salil M@francescobianco Thanks 😊
Thanks @Deadpool2000 now you are mentioned here https://github.com/openapi/openapi-python-sdk/releases/tag/0.3.0
Reacted by Salil M@francescobianco thanks for the mention, happy to see it all make it into the release 😊
Query parameters not properly URL-encoded (pandas data pipeline)
Description
Special characters break API calls when used in data pipelines.
Code snippet
Observed behavior
400 Bad Request due to invalid encoding.