So I'm trying to build an iOS app (Swift 2) which integrates FitBit.
Once the user open the 'Walks' page, the user should be able to see his daily number of steps.
Ideally, we do not want every user to register to FitBit.
So I'm trying to figure out if there is a way to fetch the data from your Fitbit directly, rather than calling the Fitbit API every time. I only require the number of steps walked daily.
TIA!
Currently there is only one way to fetch data from FitBit, Oauth 2.0
API. There is no other way. So it is not possible to fetch FitBit data
without SignIn.
If you want to integrate FITBIT OAUTH 2.0 API, Follow step by step FITBIT tutorial
https://appengineer.in/2016/04/30/fitbit-aouth-in-ios-app/
The short answer seems to be: No.
"The Fitbit API" is an HTTP OAuth rest api, which allows your server (or http-client) to exchange data with the Fitbit servers.
To the best of my knowledge there is no other API or official way to get to this data. Also fitbit does not currently write to the HealthKit Api, so it is not possible to get step data that way. According to this article:
https://gigaom.com/2014/12/24/how-to-use-a-fitbit-with-apple-health/
there should be some workaround, but I have not tried this trick, and it might have other disadvantages and require your users to install other apps on their phones. I imagine that the dataexchange between the fitbit and the phone through bluetooth would be encrypted but that is purely speculation on my side :-)
We have chosen to use the official fitbit Api which has excellent documentation and is rock-solid. Good luck in your endeavors!
Related
I am trying to use FitBit api in iOS application. I have a fitbit device and I am trying to create an iOS app that connects with the FitBit api and gets my data back. I am trying to implement OAuth2.0. I already have the client ID but I have been stuck. I am not sure how to proceed with this. I have read the documentation on how OAuth works and how fibit works with OAuth2.0 . My problem is I don't know how to open the fibit api authenication by the user, and how to get the access token. How do I proceed after getting the access token.
I am a noob to this, so I would appreciate if somebody can guide me how to go with that. If someone can guide me to similar projects it will be awesome.
Thanks
Implementing OAuth isn't a simple task. I started with Christian Hansen's OAuth Example and modified it to work for my project (his is for Google, but it can be changed to work with FitBit or anything else).
You can also check out one of the many OAuth Client wrappers on GitHub. Those two should get you close enough that you can start asking more specific questions.
I'm having some trouble understanding the Instagram API and can't seem to find a clear answer online. What is the difference between Server-side flow and Implicit flow in terms of security? I understand there is an additional step for exchanging a code for a token when using Server-side.
I am in the middle of developing an IOS app that uses the server-side flow. I am storing the client-secret within the IOS app itself and am not using an actual web server for any part of my requests. Does this method pose any security issues as the API states: "You should never ship your client secret onto devices you don’t control". Do all IOS apps using the server-side flow have a matching server side component or am I missing something here?
The method above is working for me and I am able to access the instagram API. However, I am now running into the 30 like per hour limit and want to figure out how to lift this. I understand that I need to send a signed request to the API using X-Insta-Forwarded-For header. Can this be done within Swift/Objective-C? I am having a hard time find a method for sending this information. The closest I have come to an answer is in the following post: Instagram Signed API Call from iOS
Can this be done? Thanks for the help!
I am currently building an app where they require all their users to be able to view their feeds only.
I looked at a lot of tutorials online which talk about the new api v1.1 of twitter and now authentication is required at all times.
I see a lot of examples and even successfully followed several of them like
http://www.appcoda.com/ios-programming-101-integrate-twitter-and-facebook-sharing-in-ios-6/
I even saw a tutorial posted on the twitter dev page.Following all of these focused on a few key elements
Using ACAccount to retrieve the account settings of the current user
Using the SLRequest to encapsulate the HTTP request made to the twitter api
Retrieving the data in JSON format, parsing it and presenting it to the user
Well my question is, I do not want user specific feeds. It's like a company updates their twitter regularly, users using the app should get feeds regarding the company. So I was wondering if there was a way, the app provides some default or hard coded authentication information ?
Is there some sort of tutorial, library or anything out there to help me move in the correct direction ?
Thank You for your time and help.
Your going to want to implement the following API call to get that information:
https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline
Once your application is authorized you can make a call to,
https://dev.twitter.com/docs/api/1.1/get/statuses/MorleyGaelsGAA.json
That should give you the information you're looking for.
I need to add to my iPhone app a log-in btn through Tripit.
I understand that I need to connect through OAuth and then integrate Tripit API.
But I don't understand what is going on, which part of the code (of both OAuth and Trippit) should I implement? and where (is the whole OAuth code with the log-in supposed to be called when pressing the log-in btn?).
Does anyone have maybe an example? Or a lighter explanation for the API for ios?
OAuth is used to connect your app to the user's Tripit account. After connecting, you will have OAuth tokens to store and use when making the API requests. Here is some information from a Tripit person on suggestions for OAuth and JSON libraries to use on iOS.
Could anyone please summarize the differences between Twitter's REST API and its Streaming API?
And does either of them uses Push technology?
The REST API lets you query or modify a user's account. You don't need their permission to query their account, you do need it to modify their account. They provide permission through OAuth authentication.
The streaming API delivers tweets based on search terms or for specific users you request, along with info about the author, in real-time. You do not need the tweet author's permission. You must log into some Twitter account to use streaming, using either basic or OAuth authentication.
Neither uses push, but streaming is a continuous net connection, so it is real-time delivery, making it functionally similar to push.
For anybody coming to this more recently, The REST API (v1.0) has now been retired with v1.1 being the only version. This Does now require authentication for everything, including reads.
Authentication required on all endpoints
In version 1.1, we're requiring applications to authenticate all of
their requests with OAuth 1.0a or Application-only authentication. Not
only will this visibility allow us to prevent abusive behavior, but it
will also help us to further understand how categories of applications
are using the API. We'll apply that understanding to better meet the
needs of developers as we continue to evolve the platform. At this
time, all authentication requires user context, but in the coming
weeks we'll be pushing out support for a form of authentication not
requiring a user context.
Actually you can use search through the REST API as well. For example it's the only way to combine geo AND query keyword, while the Stream API can only use OR logic.
I think it's about defacto push streaming as Adam Green has said.