OAuth redirect_uri

[WORMSS]

Hello,
Let me prefix this with, the answer is most likely "we cannot tell you this due to security" ... BUT
There is a app that my gym is basically forcing us to use. mywellness. They have a whole page about tying a bunch of other API services together. One of them being FitBit.
I suspect they have gone through a domain name change, or they have changed endpoints on their server. And have broken all their integrations. Again one of them being FitBit, so the return_uri query they are sending to the fitbit auth server is wrong.

I was hoping I could get the correct return_uri for the "mywellness" app. client_id 228YHF. 
I know this is usually stored in the developers portal for other oauth integrations I have built myself, but since I didn't write the mywellness app and they are incapable of making it work, I would do it myself

The one they are trying to use is 

https://v1.mywellness.com/cloud/thirdpartiesactivity/fitbit/returnuri

 and it's reported as incorrect.
I just want to reconstruct the correct url so I can get things integrated properly.

[GordonFitbit]

Hi @WORMSS 

If the problem is with the redirect URI, then the problem exists for all of their users and not just you.   My recommendation would be to go back to MyWellness and have them fix the problem.   I can try to reach out them as well.

[WORMSS]

Already did.. I was ghosted.. So I was just going to take the url they are trying to make me go to. Change the query value to the redirect_uri that their dev account believes is the correct, and then when the webpage tries to direct me to the url, I will take the grant code, and then redirect it to their new endpoint.. 
Basically do a "man in the middle correction" for myself.. If it works, it works, if it doesn't then it remains broken for everyone.. 

I just need to know what the old/original redirect_uri is.. I tried a few variations of possibilities, since their other integrations all follow a similar naming pattern but it's plagued with various case sensitivity changes, some have underscores, some don't.. but, for all I know, they may not have even been called 'mywellness' back when all this was setup. I know they have a `v1` subdomain, but don't seem to have a v2. All I know is their client id is 228YHF, and just trying to do the best I can with a crappy hand.

[GordonFitbit]

What error are you getting when you attempt to go through the authorization flow?  And which operating system are you on?

[WORMSS]

{"errors":[{"message":"redirect_uri_mismatch: The redirect URI provided is missing or does not match partner callback url"}]}

Windows, but a url is not operating system based. 

https://www.fitbit.com/oauth2/authorize?client_id=228YHF&response_type=code&redirect_uri=https%3a%2f%2fv1.mywellness.com%2fcloud%2fthirdpartiesactivity%2ffitbit%2freturnuri&scope=activity+nutrition+weight+respiratory_rate+sleep+oxygen_saturation+profile+heartrate+cardio_fitness&expires_in=31536000

[GordonFitbit]

I heard back from their support team and was told the following

Hi Gordon, I’ve just tried and I confirm it doesn’t work anymore from site https://v1.mywellness.com/

Please connect it from Technogym App while we fix this.

Are you able to try their mobile app?

[WORMSS]

Never been told about their mobile app, only their website. I'l look into it.
Out of interest, which address are their support team responding to? I've not heard anything from them for over 2 weeks

[DonDickinson]

You must have access to the "Manage my apps" (or whatever it's called) area of the developer portal. Assuming you can get there, you can specify the endpoint for your return uri. As long as your app is sending the return URI and it matches what you have setup, it should be changeable and work correctly.

[WORMSS]

@DonDickinson I believe you have misunderstood the problem.

[GordonFitbit]

This is the support email address I found in the Google Play store.   They replied to me in just a few hours.

mywellnessapp@technogym.com