There are different options for registering redirect URIs with your client credentials. Please note that all redirect URIs for your production credentials need to be https.
Register all redirect URIs fully
This is what is encouraged on the registration form and is what most third parties do.
Register just the host name
If the client app is registered with a redirect uri that is just the host name, then any redirect uri at that host can be used. So, for example if the following redirect uri is registered: https://thirdparty.com
then all of the following redirect_uris will work:
https://thirdparty.com/oauth/callback1
https://thirdparty.com/callback2
https://thirdparty.com/anything-else-as-long-as-the-host-is-the-same
If you decide that this approach might work for you - you can perhaps handle the URIs by registering all of the redirect URIs in one of your domains and then redirect again to the appropriate domain.
Register no redirect uris at all (sandbox only)
If the client app is configured with no redirect_uris, then any redirect_uri can be used. This is less secure than specifying redirect_uris. The redirect_uris give an extra level of security because they prevent somebody using someone else's stolen client credentials (because we would never redirect to their domain - they would also have to have control over the user's DNS to get round that!). Because of the potential risks, we only allow this option on the Sandbox API.
When registering for credentials, if you do not want any redirect URIs registered request "no redirect URIs" in the notes field.
If you are using the member API and require any changes to your redirect URIs then please contact our Engagement Team.
Please note that redirects are optional data as part of the OAuth code exchange. If a redirect URI is included then it has to exactly match the one that was used in the authorization URL. For more information please see our other FAQs in this category.
Was this helpful?