json response
Hi there,
Is there a change in the json response when I do http write to a channel ?
I send:
POST /update.json HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Host: api.thingspeak.com
Connection: close
Content-Length: 102
apikey=xxxxxxxxxxxx&field1=-4.803&field3=18&field4=91&field5=109&field6=56&field7=0&field8=7
and I don't receive the normal response
I get sth like:
'unsafe-eval'; style-src 'self' https: 'unsafe-inline'; connect-src 'self' https: https://*.mathworks.com https://*.thingspeak.com https://*.omtrdc.net https://*.demdex.net; frame-src 'self' https: https://*.mathworks.com
5 Comments
Time Descending
Here's my CURL request:
curl --request POST --url https://api.thingspeak.com/update.json --header 'Content-Type: application/x-www-form-urlencoded' --data api_key=REDACTED_API_KEY --data field1=34959
or the version of it with the params sent in the query parameters:
curl --request POST --url 'https://api.thingspeak.com/update.json?api_key=REDACTED_API_KEY&field1=23423' --header 'Content-Type: application/x-www-form-urlencoded'
and the response I get back:
{"channel_id":2778777,"created_at":"2026-11-05T15:21:39Z","entry_id":15,"field1":"34959","field2":null,"field3":null,"field4":null,"field5":null,"field6":null,"field7":null,"field8":null,"latitude":null,"longitude":null,"elevation":null,"status":null}
This matches the documented behavior.
Can you please share your CURL request (with your channel's API keys redacted)?
Hi,
curl works fine.I also tried postman which also response well. The device (gsm gprs module) does not receive proper data. And this first happens at 10/10/2026.
Regards.
curl -k --request POST --url https://api.thingspeak.com/update.json --header 'Content-Type: application/x-www-form-urlencoded' --data api_key=REDACTED_API_KEY --data field1=0
{"channel_id":3402447,"created_at":"2026-11-05T15:52:34Z","entry_id":3039,"field1":"0","field2":null,"field3":null,"field4":null,"field5":null,"field6":null,"field7":null,"field8":null,"latitude":null,"longitude":null,"elevation":null,"status":null}
We haven't made any changes on ThingSpeak around 10/10/2026. Your experiments with CURL and POSTMAN confirm that things are working as documented.
Did your mobile provider change something? If you put your device on a WiFi network that does not go through your GSM/GPRS network, does it still see the issue?
Do you mean a change from what is written in the doc? I'm not aware of any changes from the published doc.
Yes, It looks different
I don't see any "created_at": "
I use this to extract the time
Sign in to participate
Tags
