@JLucben,

My initial advise is to create a custom application and the user tokens, although i knew it was possible to obtain and reuse the EZ-Robot tokens.

I didn't do it before DJ's approval.

So the code below is the short and effective answer:

        public void TwitterTest1()
        {
            var tokens = new Twitterizer.OAuthTokens
            {
                AccessToken = EZ_Builder.Common.GetRegistryEntry(EZ_Builder.Constants.RegistryKeys.TwitterAccessToken, ""),
                AccessTokenSecret = EZ_Builder.Common.GetRegistryEntry(EZ_Builder.Constants.RegistryKeys.TwitterAccessTokenSecret, ""),
                ConsumerKey = EZ_Builder.Constants.TwitterConsumerKey,
                ConsumerSecret = EZ_Builder.Constants.TwitterConsumerSecret
            };

            //Tweet
            var twitterResponse = Twitterizer.TwitterStatus.Update(tokens, "This is a Tweet!");

            //Direct Message
            Twitterizer.TwitterDirectMessage.Send(tokens, 844385345234, "this is a direct msg!");
        }

although Twitterizer's API allows read direct messages, ez-robot application is not authorized to read the direct messages.

happy code!

My draft plugin is using user token with framemork tweetinvi , its working fine but it will be better just as cleaner integration to reuse the EZ-Robot tokens but they don't allow to day to access direct messages.

One limitation of tweetinvi to day is that you cannot send direct messages with file attachments. Do you know other one with this feature

Jean-Luc

@Jlucben,

coretweet: https://coretweet.github.io/

wiki: https://github.com/CoreTweet/CoreTweet/wiki/Using-REST-APIs

check the last example.