cancel
Showing results for 
Search instead for 
Did you mean: 

API query invalid in SnapLogic, but valid in Postman

Garrett
New Contributor II

Split out from: 401 Error using Https in API REST GET call

Did you ever solve your issue?

I am experiencing something similar. To answer the question the User-Agent can be anything. Something like SnapLogic/version# replacing the number.

My issue is that when I run it in Postman I get results.
When I run it in SnapLogic the Server is saying that the query is invalid.

17 REPLIES 17

Garrett
New Contributor II

Ah that explains it. Unfortunately, I have no control of the receiving endpoint. It is an Oracle Endpoint.

Maybe it could be added as an option to the Rest Get? To be able to encodeURIComponent (encode query parameters).

Thanks!

Yes, we could have an option in Rest Get to control how the query parameters are encoded. Or is the workaround using encodeURIComponent in the Service URL expression sufficient for your needs?

Garrett
New Contributor II

The workaround works for now.