400 Error making HTTP request with JSON in Pipedream HTTP builder

Help
,
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi all, I have an incoming trigger with a HTTP payload being delivered to pipedream, to which I am stripping some fields and converting to a HTTP POST request destination with some data from the original payload.
I am getting a HTTP 400 bad request on the POST send, to which the receiving end seems to only accept data in their specific format.
Could anyone lend an eye to see what could be wrong with my json query for the HTTP POST trigger send?

2

Destination: https://url.url.url/api
API-KEY: testkey1234
Request example format accepted

{
  "testMode": true,
  "utc_located_at": "2022-01-25T02:00:00.000Z",
  "id_dev": "1234",
  "lat": -3.87,
  "long": 1.20,
  "speed": 1.0,
  "satellite": 0
}
3

My pipedream trigger to send:

HTTP Request config
POST https://url.url.url/api
Headers: API-KEY testkey1234
User-Agent pipedream/1
Content-Type application/json

Raw Request Body

{“testMode”: “true”,“utc_located_at”: “{{steps.trigger.event.body.Records[0].Fields[0].GpsUTC}}“,”id_dev”: “{{steps.trigger.event.body.SerNo}}“,”lat”: “{{steps.trigger.event.body.Records[0].Fields[0].Lat}}“,”long”: “{{steps.trigger.event.body.Records[0].Fields[0].Long}}“,”speed”: “{{steps.trigger.event.body.Records[0].Fields[0].Spd*0.036}}“,”satellite”: “0”}

4

If I click the RESULTS and Inputs for HTTP Request config, I can see the data is being pulled, but the end destination is still not accepting with a 400 Bad Request. Can anyone spot anything? I think it might be an additional { } required, but pipedream doesn’t accept it (Invalid or unexpected token)

Body RESULTS

{"testMode": "true","utc_located_at": "2022-12-13 00:13:08","id_dev": "1234","lat": "-26.652","long": "153.08","speed": "0","satellite": "0"}
5

Dylan Sather (Pipedream) : Could you do me a favor and visit your workflow’s Settings tab, and share the workflow with Pipedream support? If you can DM me the workflow URL and tell me the step in the workflow where it’s failing, that would help.

Do you mind if I test the step myself to see if I can help correct it?

6

Done - yes please test.
I have set the trigger to do 2 min updates so it’s constantly pushing data every 120 secs

7

Dylan Sather (Pipedream) : FYI here’s how we solved this, in case encounter the same issue:

  1. We modified the JSON being sent from “raw” mode to structured mode in the Pipedream HTTP request builder.
  2. Some APIs are strict with the type of data that gets passed, so I also changed the string “true” to the boolean value true, and changed one number to a string (you’ll see one of the values wrapped in String()). This made the types of data being passed consistent with the API docs.