#1

I just became approved for a dev acct for 1 handle in our organization.
I assumed I would need to apply for a dev acct for each handle our org uses.

Now after reading in this forum, it appears our org should have just 1 dev acct, and create multiple apps (apps named for brand recognition and specific purposes, etc), and for each of our handles that needs to use an app(s), that handle does a 3 legged auth process with each app, and the app captures the access token & secret of handle[i], saves those access tokens in a data storage, and then the app can post status updates on the handle’s timeline (as described here: https://developer.twitter.com/en/docs/basics/authentication/overview/3-legged-oauth.html).

  1. can someone confirm this is the best practice?

  2. Can I suggest Twitter add this type of explanation to the pages when you apply for access to the Twitter API (https://developer.twitter.com/en/application/login?useCase=11)? A separate url / article that explains some typical use cases for organizations using a team dev acct would produce a better understanding

  3. Now I understand the dev acct should be established under the main handle for the organization. Can someone confirm I use this url (https://help.twitter.com/forms/platform) to transfer the dev app to a different handle?

#2

I can confirm your logic here. You should keep it to 1 dev account per organization, and create a different Twitter developer app for each use case. It is best if these Twitter developer apps are all owned by the organization account.

This is a great recommendation. Authorization is tough, and we know that. We have recently improved our 3-legged oauth documentation, but a tutorial would be very helpful. I will discuss this with the team.

I can confirm this. Be prepared to have the app owner approve the transfer.

Let me know if you have any other questions!

1 Like
#3

Thank you.

I am the app owner. What do I need to do the be prepared to approve the transfer? Will all communication come thru email, or will there be direct messages in twitter that I would need to respond to, in order to complete the transfer?

Will the main handle account, (which the dev account is being moved to) need to do anything? A different member of the org watches that account, so I will need to advise them what to watch for…

#4

All transfer-related comms will come via email. You will need to confirm the change on both the requesting side and the currently owning side to complete the transfer.

Platform Operations transferred ownership of my app to my organization's parent acct, but without developer access
#5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.