(To preempt any concerns with what I’m about to discuss… As per “Automation Rules and Best Practices” https://support.twitter.com/articles/76915, I have extensively disclosed (and exposed) my proposed application with Twitter support, and was told that “you should be fine.” (And, subsequently, “We look forward to seeing what you develop.”))
I’m developing an app through which I intend to publish news items to multiple Twitter accounts from an automated, non-interactive batch process. The same specific accounts will be published to each day (known quantity/identity), with new accounts being added over time, but existing accounts rarely if ever eliminated.
I created a test Twitter Application, revealing the Consumer key/Consumer secret and Access token/Access token secret necessary to publish to my test account (which I have successfully done).
If I understand this correctly, I would use the same Consumer key/secret when publishing to each account, but a unique Access token/token secret for each account. How do I determine the token/token secret for the other accounts that I will publish to? Will the token/token secret be “permanent”, or will they change with each batch run (or even with each POST)?
Or do I have to create a unique Twitter Application for each account that I wish to publish to? (Which, while painful to initially set up, will be trivial to implement in the batch process.)
Or am I fundamentally misunderstanding Twitter Applications? I’ve looked at the “Which authorization path should I choose?” document, but (being new to Twitter) it’s a little opaque to me at this point. Does the batch nature of the process necessitate that I become intimately familiar with oob?
Thanks for your help!