Does anyone have experience calling pCloudy APIs to get back the device list? I managed to get back a response however, the devices that was returned was limited. I have contacted the support team but they are not responding.
Here is the API documentation:
https://content.pcloudy.com/apidocs/index.html#get-device-list
Thank you in advance!
Related
I am trying to access the NEST camera devices using SDM API. to perform this I have followed the steps mentioned here "https://developers.google.com/nest/device-access/authorize#link_your_account".
So far I am able to get the authorization code and got the access token also, but when I am trying to get the devices using the access token, it is showing me blank.
the google documents are also not so much helpful and the process of registering and accessing is cumbersome.
If anybody has done that, please share your thoughts. I really need some help on it.
thank you in advance.
When you were authorizing your app you should have seen a dialog where you authorize the scopes and choose which Nest devices you want to have access to. If you didn't choose any devices this is what would happen.
I write an application that uses the api of iHealth. Scales, blood pressure monitor, and devices like that by iHealth send there data with Bluetooth and smartphone apps to the internet cloud of iHealth. Therefore a user of this devices has a user account in the iHealth internet cloud. There he can login and see his data. My app uses the iHealth api to get the data from this cloud. The user of the devices gives mi the right to access his data by OAuth 2 and after receiving the access data I ask for the data of the user with the given client id.
Well, here comes the problem. As a result I get a JSON-Object of measuring data without any data. That means there is no error message, everything seems fine, except that there are no data of this user. It's no kind of error documented here:
sandbox.ihealthlabs.com/dev_documentation_ResponseFormatAndErrors.htm
Http status is good too (200).
I don't use any optional restrictions like asking for data of only certain time.
An explication would be that the user still hasn't used his devices and the cloud therefore doesn't has any data. Unfortunately this is something I can't influence: My app is still not ready and therefore I only use the sandbox cloud offered for development (http://sandbox.ihealthlabs.com).
The sandboxuser can't use the smartphone apps and therefore I can only read the data that are yet there in the cloud. Of course I can't test without data. Who could develop without reciving data? There has to be an error. Maybe a rather silly error. I asked more than 9 days ago the support but still haven't got any answer.
Getting JSON data from the cloud with the api for blood pressure (openApiBP) (the XX-parts are abbreviated id, token, ...):
http://sandboxapi.ihealthlabs.com/openapiv2/user/d7XX..XX9f/bp.json/?client_id=a6XX..XXbe&client_secret=2bXX..XX3f&redirect_uri=http%3A%2F2Flocalhost%3A8082%2FTelemedicina%2Fdispositivos.html%3Fregreso%3DiHealth&access_token=u8XX..XXyw&sv=6cXX..XXcf&sc=deXX..XXcf
The answer to this (w/o any change) is just:
{"BPDataList":[],
"BPUnit":0,
"CurrentRecordCount":0,
"NextPageUrl":"",
"PageLength":50,
"PageNumber":1,
"PrevPageUrl":"",
"RecordCount":0}
Using the Api for Weight (OpenApiWeight) has the same problem as the OpenApiBP.
I have read the documentation more than once and searched for an explanation in the web.
As you see I ask the api and get this maybe correct but useless answer for development purposes. Any idea? What do I miss?
Update:
An iHealth Lab tecnican answered me. In the sandbox is just now user data. My way of asking and the recifed answer are therefore correct. It's not an error. To get data the application has to be registered for the real world. He didn't explain how to test with this limitation of the sandbox.
I let the the answer of the iHealth Lab api technician speak for itself:
"The sandbox does not provide any actual user data. If you want actual live data you will have to register a new application at developer.ihealthlabs.com."
If this is the answer to my question of why not reciving any data means there is really no data that I could recive.
Thanks to all that tried to help me, especially Scott Lawson. I hope this answer will help others. Knowing this a few days ago would have saved me a lot of time.
I was wondering if it was possible to detect what song a user is listening to from his/her current active device via the spotify web api.
Thanks.
I know this is an old question, but there is a new beta API endpoint available that supplies this information. It does have some bugs that I've noticed though.
Stations only: If you change stations, you have to restart Spotify to get the API endpoint to update and continue updating.
According to bug reports, it lags behind 20 to 30 minutes at random. I haven't had that problem, so it may be fixed.
GET https://api.spotify.com/v1/me/player/currently-playing
Docs: https://developer.spotify.com/web-api/get-the-users-currently-playing-track/
This is not possible using the web API. If you're writing a Mac app, you can use the Spotify Desktop Client's AppleScript API to access the current track. If the user is scribbling to Last.fm, you can use Last.fm's APIs. Otherwise, this data is not accessible.
I downloaded Nokia Counters and I dont understand how do they get sms count and call durations if there is no API that could support this?
Do they have any extra APIs?
Most likely they have deeper access. After all, it is only for their devices which means that they can not only exit sandbox, but access their own proprietary API.
It is similar to Youtube app, Adobe Reader app and deep links to marketplace.
I would really want to get access to such API :/
According to this blog post the new messaging system should be accessible via the API (fql/graph) for non developer account as of end of November. It still gives OAuthException with message "You must be a developer of the application".
I was unable to find any updates on this issue from Facebook or other sources. Anyone knows what is going on with this and when will it be accessible?
There was a bug opened on the subject, anyone who has interest in this might consider promoting it.
Going to answer my own question, according to the response on the bug seems like the official answer is:
"We said it would be published but it wasn't, so just wait until we say it will be published again".
Are you trying to read messages or send them? It's still not possible to send them but reading them should work for any app now