+4Hi, is there a way to authorise multiple subdomains for the API in the "Authorization Callback Domain" section ? Or add a comma separated list of domains ?
For exemple I want to be able to authorise, foo.my-domain.com and bar.my-domain.com.
Can I just authorise *.my-domain.com in the settings ? Or I need to create a Strava account for each subdomains ?
Thanks
Best answer by Elliott
Hi there,
At this time there is only support for one subdomain. A second one would require an additional account & app.
Hi there,
At this time there is only support for one subdomain. A second one would require an additional account & app.
+1I understand different accounts for different appls. But if I have an app in production under www.... address (and authorisation callback points at this address) and have a current build in localhost (where authorisation callback points at the localhost.. address) it seemed to work for me only days before. Now my under-construction build on localhost - is not able to retrieve data from strava. Is there a way to have both externall www. adress and localhost accepted for callback?
+4In the past I thought that localhost was whitelisted from the authorisation callback but it may have change since...
+1Thx. But this exactly is the point. If I swich this, my production side will not work for the time of the development checks (= localhost Callback).
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
