IFTTT + HTTP Blynk's API

Hy, love you introduced an http/s API.
I immediately used it in IFTT and works great with the GET method.
To get data from blynk cloud I used IFTT & Launch Center. Is there an easier way?

How can I use it with the PUT method ?

Can I change the value of a Virtual Pin in IFTT?

Thanks :smile:

Sure. You need just to change METHOD TYPE to PUT and send value you want to send. For instance

["1"]

to set button to ON state. In general it is totally the same as GET but it is PUT + value to send.

Hi Dimitry,
I’m not familiar with JavaScript so much, but I’m trying to update a pin from Matlab’s webwrite funcrtion( REstful webservices). I’ve trieds to use it with the url:
‘http://private-anon-b3c7b2d2a-blynkapi.apiary-proxy.com/’ auth_token ‘/pin/’ pin, and sent ‘data’ as ‘1’.
but the connection timed out every time
Can you help?

Use the local server address. You are using some mocked up url from apiary. Check the production tab.

Even when I use the production tab, and just eneter my token and pin, it says:
Unexpected content type. Expecting application/json

My final goal is to update a pin via Matlab (Matlab has the webwrite function which can update Restful, for a given url and data). I only know matlab well, and npt any of the other languages, andi’m not familiar with all those terms. All i need is 3 input paramters to enter to the Matlab’s webwrtie function, in order to update a pin.

I keep getting “Unexpected content type. Expecting application/json” when I try to PUT something. I see it in the documentation examples and with my own local server.

What am I/are we doing wrong?

Thanks!

How do you try to PUT something?

Hi, same here. But the GET works normally.

I’m trying with 2 different firefox extensions.

I have same issue with firefox, but curl works fine so I have feeling that this is firefox/plugin bug.

Thank you for your reply, I didn’t think about FF’s fault because Swift also sent me a parsing error.

Anyway, with curl, I got a hang for 5 minutes (and counting), it seems not to close the connection. But I think it should be another thread.

The GET responded immediately

This is correct. As it is keep-alive connection. You may turn-off it by adding additional header.

That’s strange. Cause I have a bunch of test for that. Anyway I’ll have a look.

@axel50397 @ivale @matan.benyamin I found bug. I had a very small limits on header size. I was expecting that HTTP API will be used mostly from hardware so didn’t expect big header size. Browsers add a lot =). Thank you for reporting! We will deploy fix in few days.

@axel50397 hanging also fixed.

So, is it can be possible that my problem (see: [SOLVED] What is wrong in my http request (method PUT)?) was because of this bug?

Yes. It will be fixed also.

@Dmitriy Thank you for your quick reaction