Health API - Signing request

Former Member over 4 years ago

Hello all, sorry for my english, it's a google trad.

I am unable to send a request via the health API for a webapp. I would like my users to be able to synchronize their activity files (fit) from their kid connect account to their space on my website.

Where I am :

I manage to connect via Oauth1.0

I receive a json ping for each new activity that looks like this

{
  "activityFiles": [
    {
      "userId": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
      "userAccessToken": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
      "summaryType": "GPX",
      "callbackURL": "https://healthapi.garmin.com/wellness-api/rest/activityFile?id=11607627"
    }
  ]
}

now I need to recover the file, but I have an error {"errorMessage": "Invalid OAuth signature."}

However, using the page https://healthapi.garmin.com/tools/oauthSignRequest I get exactly the same Oauth1.0 signature and the same http authorization header... Then i do not understand.

Another problem is that on this page is required the parameters "upload start time" and "upload end time", which are added to the requested url with a formatting error (note the question mark in front of uploadstarttimeinseconds while this is not the first parameter)

healthapi.garmin.com/.../activityFile

Who can help me ?

Top Replies

RTF-GUIDE.DE over 3 years ago +2

Hey,

after a long trial- and error-session we managed to create an successfull OAuth-Signature to geht the activity files:

First the correct URL for building the BeseString is https://apis.garmin.com/wellness…

All Replies

0 peterdedecker over 4 years ago

there are very few people (=noone) in this forum whom have experience with the health api, for questions your best bet is to use this email address: [email protected]

0 Former Member over 4 years ago in reply to peterdedecker

thanks a lot, but I think they are dead....

0 RTF-GUIDE.DE over 3 years ago

Hey,

after a long trial- and error-session we managed to create an successfull OAuth-Signature to geht the activity files:

First the correct URL for building the BeseString is https://apis.garmin.com/wellness-api/rest/activityFile
Then we got it working with the following array for the SignRequest:

'oauth_consumer_key' => YOUR_CONSUMER_KEY
'oauth_token' => USER_ACCESS_TOKEN
'oauth_nonce' => uniqid(),
'oauth_signature_method' => 'HMAC-SHA1',
'oauth_timestamp' => time(),
'oauth_version' => '1.0',
'token' => $query['token'], // TOKEN from the Activity-Files Ping
'id' => $query['id'] // ID from the Activity-Files Ping

I hope this will help you and other developer and perhaps garmin could make a really necessary update to their docs.