API Connector only allows lowercase query parameter names

[ndmoses]

Hi, I’m using the API Connector to access one of my REST API data sources in Wappler. In the Query Parameter screen I try to enter the parameter name in the correct case userName, but the app converts it to lowercase - username. Is there any way to prevent the case conversion?

Thanks,
Neil

[Hyperbytes]

yes you are correct if using app connect api component. the component is parsed through DOM so are converted to lower case. This does not apply to server api parameters which I would recommend you use where possible anyway for security reasons. This has previously been discussed at length on the
forum

[ndmoses]

Thank you for the reply. I will search the forum for the discussion.

[Hyperbytes]

Think this is the most important one

API Data Source - Help Needed

I am testing how API works. Read all the docs and some topics here. Then in a new page I prepared the API Data Source for the connection to a test environment of Amadeus (Travel GDS). The endpoint is https://test.api.amadeus.com/v2/shopping/hotel-offers One mandatory parameter is CityCode = PAR (for Paris) The header authorization has to be Bearer + Token. In the Amadeus test environment the token can be generated online and expires after 30 minutes. In the bottom line I will post a newly gen…

[George]

Btw we will soon be improving the API connector to allow also mixed case parameters

[benji.fergy]

Hi!
New user, still muddling my way through on a trial version to see if Wappler will suit my needs. I’ve been able to find my way so far with the assistance of this rather excellent forum and community.

Just wondering if (as George mentioned above) the API connector has been updated to allow mixed case parameter names? I seem to be able to set the parameter names as mixed case and retrieve the schema, but once I save the schema it seems to revert them back to lowercase…

Thanks in advance for any assistance!

Cheers,
Ben.