Skip to main content
Solved

Received HTTP response header: 'HTTP/1.1 401 Unauthorized' when using Strava API


Hi all, I am trying to access my Strava data specifically where I have ran/cycled for some data vis.

I have added Strava as a web connection according to these instructions: https://hub.safe.com/publishers/gerhardatsafe/web-connections/strava

While in the 'Managed Web Services' I have added in Client ID and Client Secret and testing the connection seems to be successful.

I have also added it as a Web Connection/Service.

When I run the HTTPCaller transformer with say https://www.strava.com/api/v3/athlete (or whatever else in http://developers.strava.com/docs/reference/) and put in authorization parameters into the Headers section:

 

the translation log seems to indicated that the HTTP connection is unauthorized:

 

I have been trying to figure out where I have gone wrong for hours - if someone could please point me in the right direction, it would be massively appreciated. @gerhardatsafe do you have any thoughts yourself?

 

Cheers

Best answer by gerhardatsafe

Hi @cleo,

When you use the Strava Web Connection you do not need to manually set the Authorization Header. Once add and select a new Strava Web Connection under the Use Authentication parameters the correct Authorization Header will be added all of your requests:

 

 

View original
Did this help you find an answer to your question?

4 replies

david_r
Celebrity
  • March 30, 2020

I trust you don't actually have any square brackets around the token value? Sample Authorization value:

Bearer 83ebeabdec09f6670863766f792ead24d61fe3f9

See also: http://developers.strava.com/docs/authentication/#accessingtheapiusinganaccesstoken

 


  • Author
  • March 30, 2020
david_r wrote:

I trust you don't actually have any square brackets around the token value? Sample Authorization value:

Bearer 83ebeabdec09f6670863766f792ead24d61fe3f9

See also: http://developers.strava.com/docs/authentication/#accessingtheapiusinganaccesstoken

 

Hey David, thanks for your answer! Yes you’re right, there are no square brackets - poor use of characters from me to indicate a value goes in there, not a literal. I have tried my access token (without brackets) still to no avail 


Forum|alt.badge.img

Hi @cleo,

When you use the Strava Web Connection you do not need to manually set the Authorization Header. Once add and select a new Strava Web Connection under the Use Authentication parameters the correct Authorization Header will be added all of your requests:

 

 


  • Author
  • April 1, 2020
gerhardatsafe wrote:

Hi @cleo,

When you use the Strava Web Connection you do not need to manually set the Authorization Header. Once add and select a new Strava Web Connection under the Use Authentication parameters the correct Authorization Header will be added all of your requests:

 

 

Thank you so much - this worked! Cheers


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings