However, on running the VoiceFlow command, it fails, and whenever I paste the link on Chrome, it displays Invalid Token,even when I’m using the correct authentication token.
I would be highly grateful to you if someone can guide me with the process of making HTTP calls to control Virtual Pins.
If you read the “Troubleshooting” section as I suggested, you’ll see that it’s better to specify the region subdomain, because the voice flow server may not resolve blynk.cloud to the same server where your Blynk project lives.
In addition, I am facing another problem with getting the value.
The Voiceflow API block requires for a ‘Header Assignment’ and object path to store the value returned(1 or 0). I am successfully able to turn on & off an LED in my test project, but not able to get the value. The API link works in Chrome and returns the status 1 or 0.
What should I do now?
Your first question sounds like one that should be directed to a VoiceFlow forum.
As far as the error code when calling the Blynk API from VoiceFlow, it’s impossible to say - without understanding more about exactly what API syntax you’ve used in the test call, which regional server your Blynk project lives on, what datastreams you have configured etc.
That kind of answers part of one of my questions, but isn’t sufficient to provide any assistance.
This…
is very confusing, because it implies that after the auth token you have &v0 followed by the virtual pin number that you are attempting to get the value of. However, in the above API call, v0 is the virtual pin number, and anything after this will be interpreted as an invalid virtual pin - which may be the cause of your issue.
I’d suggest you post the exact, unedited, API call - you can always generate a new auth token via the web console once you have things working.
I’d suggest that you re-read what other things asked you to provide and go ahead with providing that too if you want assistance with this.
It seems like you’re reluctant to provide any useful information, so I’ll step back from the discussion and let others chime-in, or let you figure it out for yourself.
This API is correct and works. So you’re saying that Voiceflow doesn’t work with it? It may be a Voiceflow bug. For example, they may expect eery param to have a value (I don’t know, just a guess), you can change it to:
