You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed is that all the calls in the examples on the first page are POST requests, which is not very RESTful. What is the logic behind that? Is it a limitation inflicted by NDC? I'd prefer this:
curl -X GET https://sandbox.yepjet.com/v1/search?type=flights&from=LHR&to=JFK&departure=2016-01-01
The text was updated successfully, but these errors were encountered:
yep, you're absolutely right.. GET should be the right one
it's POST right now because /search should support open-jaws (eg: searching for multiple flights, from A to B, to C to D, to D to E) which means that the GET query should look something like
the web framework that we use doesn't currently support those parameters, so I've been writing my own query parser, but I couldn't make it in time for the release
thank you for opening the issue!
I noticed is that all the calls in the examples on the first page are POST requests, which is not very RESTful. What is the logic behind that? Is it a limitation inflicted by NDC? I'd prefer this:
The text was updated successfully, but these errors were encountered: