Hi all I’m trying to send a webhook to AWS using sprintf(dataString, "{\"VGE\": %lu, \"PWR\": %lu}",voltage,power); and: Particle.publish("data",dataString,PRIVATE); The webhook gets through allright, however the template mapping I’m using in API Gateway gets confused with the backslash escape …

Sorry, I’ve edited my publish code, I was indeed using the same method as you’ve described. I don’t quite understand your comment regarding the need to have your values wrapped in double quotes?

I should have mentioned also, I’m trying to avoid sending the deviceID as part of the dataString to save data (using an electron) thought that since the deviceID was available as part of the webhook response I shouldn’t have to.

[image] G65434_2: I don't quite understand your comment regarding the need to have your values wrapped in double quotes? My bad, I misunderstood your actual question, hence what I said doesn't apply to your use case, since you said (and I missed at first), that this setup already works as is. …

[image] ScruffR: Where would that extra version come from? Looking at my API logs, if I include the default data in the webhook I get: { "event": "particleEvent", "data": "{\"TIME\": 1485845337, \"VGE\": 239717, \"PWR\": 0}", "published_at": "2017-01-31T06:49:01.449Z", "coreid": "2e00XXXXXXX…

Ah, I missed the documentation sorry I just needed to use {{PARTICLE_DEVICE_ID}} as in: { "eventName": "particleEvent", "url": "api_endpoint.com", "requestType": "POST", "json": { "voltage": "{{VGE}}", "power": "{{PWR}}", "deviceID: "{{PARTICLE_DEVICE_ID}}" }, "noDefaults": true, "mydev…

@ScruffR I realised I actually do have the problem that others were having now in regards to needing an integer instead of a string :frowning: I couldn’t get your solution to work: { "event": "Data", "url": "https://example-endpoint.com", "requestType": "Post", "headers": { "Content-Ty…

Since this was an “unreflected” quote from a post by @jvanier , I’d have to leave it to him (or @Dave ) to jump in. Julien seemed to be successful with that workaround. What do you get with that template? It shouldn’t matter, but how about changing Post to POST and Data to data?

[image] G65434_2: integer The device Id is not an integer. It's a string. As for the other values, which may need to be integers, why can't you handle that on AWS's side?

I’m reworking the webhook docs to add more advanced examples. The short version is that right now using the “json” key in the webhook config only allows string values. There’s a workaround to send integers or booleans using the “body” key that I’m documenting. I should post those docs by the end of…

Sending coreid using webhooks (without default data)

Cloud

G65434_2 January 31, 2017, 8:58am 9

In another post, @Dave mentioned a possible fix,although I’m not sure if it’s been implemented? Webhooks with JSON arrays or nested objects escaping quotes

Topic		Replies	Views
GET webhook response with filtering issue [SOLVED] Cloud photon	4	1102	August 26, 2019
Webhook custom templates not working as expected Cloud	11	3920	March 20, 2019
Webhooks & Parse.com Firmware	36	7571	October 21, 2015
New Feature! Webhooks! Cloud	47	14043	July 9, 2016
How to pass multiple data items from Particle device to webhook Cloud	10	5913	September 4, 2016

Sending coreid using webhooks (without default data)

Related topics