OAuth 2.0 Callback URL Matching Patterns

[FedericoArg]

Fitbit Team, we would like to know if there is way to use URL patterns when configuring the Callback URL in each of the apps.

Our problem is that we currently have a lot of different URLs that are used to access our Web application. Having to configure each one of the URLs leads to maintanibility issues and potential problems when URL is not included.

Is there any support for URLs patterns that could avoid configuring every single URL?

For example, the following pattern "https://*.domain.com/fitbit/oauth2callback" would support:

https://www.domain.com/fitbit/oauth2callback

https://client1.domain.com/fitbit/oauth2callback

https://www.client1.domain.com/fitbit/oauth2callback

https://client2.domain.com/fitbit/oauth2callback

https://www.client2.domain.com/fitbit/oauth2callback

[JeremiahFitbit]

Callback URIs will need to be explicitly defined.