HTTP REST API - I can't get the value from a PIN

Blynk Servers
1

Hi! Hope you’re having an awesome day.
I’ve been try to make requests to the REST API you guys have running on Blynk-cloud.com, I can use the isHardwareConnected and isAppConnected endpoints, but if i try to read or update a PIN value it simply won’t return a reply.

I feel like i’m doing something wrong, I’ve been looking for a solution for the past 6 hours with no answer in sight. I might be overthinking (which i do a lot), but I feel it’s something else.

Thank you in advance.

2

What commands are you sending to read and update PIN values and what responses are you getting?

3

Hi, thanks for the reply.

I’m using the one that’s in the API reference:
http://blynk-cloud.com/auth_token/get/pin

I get a 404 response every single time i request a pin status or try to update.

4

@Jose_M_Viloria this API is not yet deployed to blynk cloud as it was released few days ago. In few days it will be available.

5

Ohh, sorry… I didn’t know about that!
Thanks for the info.

Have a nice day, enjoying every single second i use the app!

1 Like
6

Hi

Sorry for jumping on this thread, but I have a somewhat related problem.

For the past few hours, I have been trying to use the Aviary interface to change the auth_token on-the-spot to test out the API, without doing any coding first. But I keep getting error 404, saying I have an invalid token.

But I know my token is valid, as it is working in my Python file and I managed to get a Button widget value with it.

Read Dmitry’s post that the API is not yet deployed to Blynk Cloud, is that the reason why I keep getting the error?

What is the interim API call we should make before the latest API is released to Blynk Cloud then? When will it be released? Thank you! :slight_smile:

http://docs.blynkapi.apiary.io/#reference/0/write-pin-value-via-get/write-pin-value-via-get?console=1

7

Old API is

PUT http://blynk-cloud.com/4ae3851817194e2596cf1b7103603ef8/pin/D8

and body ["1"].

However my recommendation would be to wait few days.

8

3 posts were split to a new topic: Invalid token with HTTP RESTful API

9