Hi there. Big runkeeper user, and also a software dev. I would like to provide my own info on my own website. So I need to auth my app but not involve my users. Can I do this somehow?
If I understand you correctly, you would be making calls to the API only on your own behalf. In this case, perform the OAuth flow once (using whatever environment you choose to set up) in which you enter your own email address and password, and save the resulting access token. Since this token does not expire, you can transfer it to your web backend to make calls to the Health Graph.
On Tue, Dec 6, 2011 at 13:19, Will Meyer <willme...@gmail.com> wrote: > Hi there. Big runkeeper user, and also a software dev. I would like > to provide my own info on my own website. So I need to auth my app > but not involve my users. Can I do this somehow?
> If I understand you correctly, you would be making calls to the API only > on your own behalf. In this case, perform the OAuth flow once (using > whatever environment you choose to set up) in which you enter your own > email address and password, and save the resulting access token. Since > this token does not expire, you can transfer it to your web backend to make > calls to the Health Graph.
> -- Chris
> On Tue, Dec 6, 2011 at 13:19, Will Meyer <willme...@gmail.com> wrote:
>> Hi there. Big runkeeper user, and also a software dev. I would like >> to provide my own info on my own website. So I need to auth my app >> but not involve my users. Can I do this somehow?
I have been able to make the whole process work, but need a little guidance on how to pass the token to Health Graph on subsequent calls, ie) after I have received and saved the token. * * Thanks, Len * * *and save the resulting access token. Since this token does not expire, you can transfer it to your web backend to make calls to the Health Graph. *
On Tuesday, December 6, 2011 3:53:13 PM UTC-6, Christopher Barratt wrote:
> Hi Will,
> If I understand you correctly, you would be making calls to the API only > on your own behalf. In this case, perform the OAuth flow once (using > whatever environment you choose to set up) in which you enter your own > email address and password, and save the resulting access token. Since > this token does not expire, you can transfer it to your web backend to make > calls to the Health Graph.
> -- Chris
> On Tue, Dec 6, 2011 at 13:19, Will Meyer <willme...@gmail.com> wrote:
>> Hi there. Big runkeeper user, and also a software dev. I would like >> to provide my own info on my own website. So I need to auth my app >> but not involve my users. Can I do this somehow?
On Tue, May 1, 2012 at 9:26 PM, Len Hardy <ljha...@gmail.com> wrote:
> I have been able to make the whole process work, but need a little
> guidance on how to pass the token to Health Graph on subsequent calls, ie)
> after I have received and saved the token.
> *
> *
> Thanks, Len
> *
> *
> *and save the resulting access token. Since this token does
> not expire, you can transfer it to your web backend to make calls to the
> Health Graph. *
> On Tuesday, December 6, 2011 3:53:13 PM UTC-6, Christopher Barratt wrote:
>> Hi Will,
>> If I understand you correctly, you would be making calls to the API only
>> on your own behalf. In this case, perform the OAuth flow once (using
>> whatever environment you choose to set up) in which you enter your own
>> email address and password, and save the resulting access token. Since
>> this token does not expire, you can transfer it to your web backend to make
>> calls to the Health Graph.
>> -- Chris
>> On Tue, Dec 6, 2011 at 13:19, Will Meyer <willme...@gmail.com> wrote:
>>> Hi there. Big runkeeper user, and also a software dev. I would like
>>> to provide my own info on my own website. So I need to auth my app
>>> but not involve my users. Can I do this somehow?
