Before publishing this bug here, I carried out tests on the registry office and on insomnia. Both working normally. This bug is in wappler and not in flow or variables!
Request:
Logs:
Can you explain what is the bug reported here? Which parameter on your screenshot has an issue?
Right now! It turns out that when they passed the query parameters in API Action (GET), it didn't send or confirm them. I don't know for what reasons. I've already tested it without it and it's working normally. Example: I went there https://api.example.com/sellers/search?ein=.... It turns out that the external api returns an error stating that the parameter is not being passed, however, when I use the same url in postman or insomnia, the request is made successfully. Note: These are the same headers, query parameters, etc...
The url is 'requestEndpoint', checks at image with logs.
So which parameter is not passed? I don’t see any query params defined on your screenshot. Sorry but i don’t fully understand what the problem you are describing is.
Most probably your API Endpoint URL is not correct:
Check your API docs and see what the endpoint should be, and then define the correct params to be sent to it.
Do you need to use GET parameters in GET methods?
Define a $_GET ein at the top of your server action
Then put the $_GET.ein in your User Name field.
Believe me friend! Check now. There are 2 actions on different routes and with the same reqendpoint, headers, etc...
Check:
It has no relation to this situation, it doesn't matter whether you use it via $_GET or via a variable in direct url.
I found the problem, it happens when the 'content-type' = 'application/json' header is sent. Wappler is not sending the query parameters correctly.
I was sending 3 headers:
Error request: accept, content type and connection. Then wappler returns API error.
Succeeded request: content-type, wappler stopped returning the error. However, this did not happen before. It's very strange.