We have received a warning from Twitter Support about something we are not able to make any sense.
Here are the mails from them
We have data showing many Twitter users that have multiple connections on their individual accounts to your app XYZ, app ID XXXXX. Having multiple connections to an single app is prohibited by the following part of our Developer Agreement and Policy: Do not do any of the following - Use a single application API key for multiple use cases Each Twitter account is only permitted a single connection to your app XYZ, app ID XXXXX.
Your customers are creating multiple access tokens for your app ID XXXXX on individual Twitter accounts. Having multiple connections to an single app (i.e.: creating multiple access tokens) is prohibited by the following part of our Developer Agreement and Policy: Do not do any of the following - Use a single application API key for multiple use cases
Your users are creating multiple tokens for the same use case by creating multiple accounts via your site. This has nothing to do with email requesting or any other Twitter permission. Each user of your service is only permitted one connection to your app per our Developer Agreement and Policy. You must fix this issue by the deadline provided in our initial notice, or you will face restrictions from accessing our API.
The deadline is in 5 days!
We use only 1 app ID for our application.
We do not use any other app ID, nor do we use this app ID anywhere else.
I am not sure how 3rd party apps like ours can create multiple access tokens to the same Twitter profile!
We do have a dashboard feature where users can add their social profiles (Twitter, Facebook, LinkedIn etc) to their Main Account but that is only to manage those profiles from a unified dashboard. All socia media management applications, including Tweetdeck, allow that and so I hope this is not what they mean.
We have not been able to get any response from Twitter support after sharing with them the above explanation.
Our last reply to them:
We are ready to make any change necessary to curb this issue immediately but we are not able to understand how 3rd party apps like ours can create multiple tokens. We haven't changed our way of authentication since last 5 years and it is not clear of how any of the processes we implement can link to creating multiple tokens. It will be extremely helpful if you can share with us the possible reasons how multiple tokens can be created. As soon as we can relate to any of them, we will make the change in our system within 48 hours to ensure we do not violate any terms.
While we still wait for their response,
I will be very grateful if someone can assist us in understanding their expectations.
Thank you in advance