What is the correct way to work with Twitter REST API and OAuth?

Question

OAuth

Good afternoon!
Tell me, pliz, is it possible to do the following with the Twitter API: there is my application (client-server) and I need to post messages to Twitter via REST without user intervention, i.e. there will be a separate account for the application, which will throw off some messages. I don’t understand OAuth authorization a bit, is it possible to do this with it? on the website of the tweeter, they seem to write only that human intervention is necessary.
I tried to register my application on dev.twitter.com - I got a consumerKey, consumerSecret, Access Token and Access Secret, wrote the code, it seems to work, the messages are fasting, but as far as I know Access Token and Secrect have a limited lifetime, and you need to how- then re-login and get them again through api.
Please write in more detail how to do what I want.

Answer 1

Access tokens are forever. It is enough to get them once. Then you can safely post. For convenience, it is better to take some library for your language.

Answer 2

Thank you! Or maybe tell me along the way, otherwise there is different information on this subject on the Internet, is there a limit on the number of tweets via the API? somewhere it says that 15 stakes in 15 minutes. And somewhere they write that this does not apply to post status (i.e. tweets)