Quota increase request hasn't been responded to in over 3 weeks

[bendell]

Hi there. We’ve had a fully functioning Twitter app (via the old developer portal) for over two years now. We’re now trying to switch over to the new portal. As part of that, we need our quota to be increased (regarding the qty of tweets we can send per hour). We sent a request via the new developer portal a few weeks ago, but we haven’t received a reply yet.

At this moment in time, our product is being restricted by the default send quota - which is resulting in many of our customers tweets never being sent.

In short this has become a super urgent issue for us. Our business is essentially crippled at the moment, whilst the default quotas are in place.

Is there anyone here from Twitter that is able to help us?

Thank you.

Ben
CEO at Missinglettr

[LeBraat]

Hello Ben,

Thank you for writing in. I have just made an adjustment to your account to let you apply via the proper elevation pathway.

Please fill out the following form again, this time making sure to select I would like to apply for elevated POST limits.
https://help.twitter.com/forms/platform

We will make sure to escalate internally once you have done so.

[bendell]

Thanks! Really appreciate the prompt reply. I’ll get that submitted now.

[bendell]

OK I’ve just submitted it. If you’re able to look out for the submission and escalate it, that would be incredible. Thank you.

[LeBraat]

Thanks @bendell,

I will escalate internally.

[bendell]

Thanks so much for the escalation @LeBraat. I’ve just received an email to confirm that the quota has been increased. Thank you!

Quick question - I think we’re still linked to our old app ID (from the old developer portal) in our production app. Do we need to get all of our users to re-authenticate against the new developer portal App ID or is there some way you guys can automatically port it over?

[LeBraat]

Glad to hear that you’ve been elevated!

Couple of clarifying questions:

When you say ‘old developer portal’, do you mean apps.twitter.com?

If so, all of your owned Twitter apps on apps.twitter.com should directly translate to the new app management dashboard on the new developer portal on developer.twitter.com. You should be able to see all of your old Twitter apps created on apps.twitter.com alongside any of your new apps created on developer.twitter.com in the new app management dashboard. All of your authorized users will be attached to your apps, regardless of which dashboard you are managing your apps through.

Knowing this, can you continue to use your old Twitter app to manage your integration with Twitter dev products and your production app?

If you would still like to transfer over to a new Twitter app, you will have to have all of your users re-authorize that app. I’d be curious as to why you’d like to do this as well.

[bendell]

Ah in that case, I don’t think I’m seeing my apps from apps.twitter.com in developer.twitter.com. What should I do?

Benjamin Dell
Founder & CEO, Missinglettr

[LeBraat]

A couple of questions:

1. Are you logged into the same account (@handle) on both platforms?
2. If so and you are still not seeing the apps in developer.twitter.com, could you please the app IDs of the apps that aren’t showing up in developer.twitter.com? A screenshot wouldn’t hurt as well.

[bendell]

Ah, I’m so silly! I just assumed the app in developer.twitter.com was a totally different app (with its own keys) to the original one at apps.twitter.com - I can see now that they have the exact same consumer / secret keys, so presumably if we’re already using those keys there shouldn’t be anything else we need to do. Let me know if I’m wrong on that assumption. If not, feel free to ignore this message - no reply needed.

Thanks again for your help!

[LeBraat]

Your assumption is correct! Very glad we could help you out here.

[LeBraat]