It's not possible to create Strava or API instance without authorization process

[hobovsky]

Hi Dan,

Maybe I am missing something, but I can see no easy way to make calls to Strava without going through full authorization process, as I always need a Token instance which is returned only by tokenExchange calls. But sometimes I'd like to make calls without authorization, for example using public token provided by application when it's created (it's enough for most of non-private segment related calls), or previously retrieved token persisted by my app.
It's not possible to instantiate a Token solely with it's string representation, I need a TokenResponse for that. Currently I work around the problem by creating TokenResponse instance on my own, but I think it would be nice to have a way to somehow initiate the work with Strava or API without the need for tokenEchange each and every time, since I already have a token. Especially because a Token is tightly coupled with a StravaAthlete, and public token has no athlete associated with it.

Is there easier way, or am I missing something in the library?

Best regards,
Maciek

[danshannon]

I think I've put in some new methods that allow for that fairly recently... I'll check when home Cheers Dan

…

Sent from my iPhone On 29 Jul 2017, at 6:10 am, hobovsky <notifications@github.com> wrote: Hi Dan, Maybe I am missing something, but I can see no easy way to make calls to Strava without going through full authorization process, as I always need a Token instance which is returned only by tokenExchange calls. But sometimes I'd like to make calls without authorization, for example using public token provided by application when it's created (it's enough for most of non-private segment related calls), or previously retrieved token persisted by my app. It's not possible to instantiate a Token solely with it's string representation, I need a TokenResponse for that. Currently I work around the problem by creating TokenResponse instance on my own, but I think it would be nice to have a way to somehow initiate the work with Strava or API without the need for tokenEchange each and every time, since I already have a token. Especially because a Token is tightly coupled with a StravaAthlete, and public token has no athlete associated with it. Is there easier way, or am I missing something in the library? Best regards, Maciek — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.