Is it possible for redirect URLs to contain non-Fitbit related query parameters?

[yeamank]

Hi all,

I'm almost at the end of building out a FitBit workflow using our team's REDCap instance (REDCap is a database application for clinical researchers developed by Vanderbilt). 

The problem I am having at this point is with the redirect URL. REDCap uses a hashing system to identify surveys in it's database. The way surveys are identified are by passing the hash in the survey query parameter in the URL. It is possible to use something called a "public survey link" which has a consistent hash. For example: https://redcap.domain.edu/surveys/?s=STATIC-HASH-HERE

However, public survey links have many drawbacks in designing databases and identifying unique participants. Because of this, it's preferred to use a unique hash in the survey query parameter for each research participant, rather than a static hash. e.g., https://redcap.domain.edu/surveys/?s=UNIQUE-HASH-HERE

That said, every time I configure the redirect using a unique hash, FitBit does not recognize my redirect URL. I have tried formatting the redirect URL as https://redcap.my-domain.edu/surveys/  to no avail.

Is there anyway for my FitBit application to support survey hashes in my URL query parameters?

[Gordon-C]

Hi @yeamank 

If you can get the static hash to work, then I would guess the unique hash would work.   I will reach out to you directly to get some examples from you.