Get Request with JSON

[toddvarriano]

1) Give a description of the problem
Creating a Get request, but no option visible to make it With JSON

2) What is the expected behavior?
Some option available to chose JSON

[eibyer]

I believe that’s only available with PUT and POST

Edit: more details here…

webCoRE Update v0.3.105.20180628: improvements to web requests, reorder variables, collapse fuel streams

The v0.3.105.20180628 update includes a few notable changes described below. Be sure to refresh your dashboard and update to the latest smart apps from GitHub. Feedback is welcome in this thread but if there are any serious issues please start a new topic. Variable reordering When editing a piston, the define section can now be reordered: [variable-reorder] Like statements, variables can be copied by holding down the alt key while dropping. Since variable names must be unique, copying a va…

[allrak]

You trying to return json that gives a drive time in seconds from google maps API?
For google maps api, that would be:
$timeInSeconds = $response.rows[0].elements[0].duration_in_traffic.value

URL to request would look something like:
https://maps.googleapis.com/maps/api/distancematrix/json?departure_time=now&origins={origin_address}&destinations={destination_address}&key={api_key}

^^ Obviously you’d need variables for “origin_address”, “destination_address”, and “api_key”

[toddvarriano]

So, looking at other examples, users would have a GET URL with JSON (at the end). Is that not need anymore?

[allrak]

No, you don’t need to specify JSON… Just a generic GET request.

[ipaterson]

So, looking at other examples, users would have a GET URL with JSON (at the end). Is that not need anymore?

Specifically, that configuration was possible in the past but it was misrepresentative. The “type JSON” there is supposed to show the format that would be used if you send variables along with the request. For a POST request, your variables would be encoded as {"key1":"value1","key2","value2"}. However, JSON parameters have never been supported or made much sense for GET requests since probably 99% of GET web requests will use form encoding (?key1=value1&key2=value2). Changing it from FORM to JSON had no effect so that field was removed. The server determines what response format to send.