#1

Hi!

We call the twitter api from more than 15 differents domains.

Before 12th june we use dynamic callback whithout any problem.

Now, on the Api setting we can add to whiltelist max of 10 URL.

Any solution for this?

Thank in advance!

Unable to add callback ur in application settings
How many call back urls can be whitelisted
#2

Hi there,

Confirming that this is an issue for our application that uses subdomains.

Is there a way to wildcard callback urls as in https://*.domain.com ?

Any other suggestions for multi-domain apps?

Looking forward to your response,
Y

#3

There is no way to do that. One alternative would be to use a URL parameter to provide the routing e.g. https://www.domain.com/?target=thetopdomain

#4

Thanks Andy,

www.domain.com is a different website in my case, but something like dummy.domain.com?subdomain=domain_name might work. However this would require investigations and changes on our side, which is undesirable.

On the off chance, is there any way to lift the limit or at least increase it?
Both Facebook and Salesforce have same callback url enforcing mechanisms but neither of them limit amount of URLs to 10. :confused:

1 Like
#5

+! for this request. If you have a site where folks are actually login into the various subdomains and credentialling is handled separately across the subdomains than I don’t think sending to one spot for authentication would work.

#6

This is a crazy limitation with 10 URL and the offered solution is not feasable because OAUTH redirections are working with SESSIONS and sessions are setting based on domain. So returner URL will not catch the proper session especially on load balanced platforms.

Twitter platform is loosing it’s popularity before and now loosing it’s developer friendly support too…

#7

Thanks for the feedback! Would be interested in your suggestion to resolve this - what would be an “appropriate” limitation?

Take the point about sessions, which some folks may not have considered. However, we’ve generally heard that a dispatcher solution is working for many situations.

Can you describe your use case in more detail?

(re: “developer friendly support” - hi! that’s what I work on! we’d love to learn more)

1 Like
#8

Hi @andypiper I’ve noticed that the limit on 10 callback URLs really limit WhiteLabel options here. Especially as the developer terms block this from creating multiple apps for a single app/whitelabel. What is the solution here when the WhiteLabel would like their own branding / name in the Twitter OAuth process?

You are not permitted to register multiple applications for a single use case, or substantially similar or overlapping use cases. Learn more about these policies here.

In this context, we define “use case” as a consistent set of analyses, displays, or actions performed via an application. Providing the same service or application to different end users (including “white label” versions of a tool or service) counts as a single use case.

#11

This is also an issue for our app for reasons similar to the original poster. We have over 30 customers each with their own separate sub-domain - i.e. https://customername.ourdomain.com, so the limit of 10 is a real problem for us. As one of the other posters mentioned both Facebook and Google require/allow your app to lock down the callback URL’s, but we don’t seem to have hit any hard limits on the number of URL’s.
Is there any update on progress to address this?

#12

Consider your use cases heard. I have passed along this use case to our product team and will make sure to update you with any material responses.

2 Likes
#13

Hi, it’s been a few months and this issue still persists. I’m not sure I understand the reason for the 10 URI limit but it really leaves every website that uses many subdomains stranded – there is no feasible work around. Could you please remove this limit and find a different approach to whatever you were trying to achieve with this? Other social networks have been so much friendlier to developers… this bureaucratic stonewalling is a big turnoff from having us integrate to twitter – in fact with our type of website we just can’t. Please address this issue ASAP.

1 Like
#14

Hello @lovincommunity - We do not currently have any updates related to callback URLs here.

Per our docs…

There is a hard limit of 10 callback URLs in the Twitter apps dashboard. Please make sure to combine your callback URLs into a single address and use query strings in your oauth/request_token request.