Example of work from 1С with Twitter API 1.1, OAuth 1.0a, HMAC-SHA1
The purpose of publication - to show how is it possible to pass the problems created for us by OAuth 1.0
This is not a complete library of functions to work with Twitter, but just an example, a couple of functions. For service functions javascript is used with help of COM-calls to MSScriptControl.

Tested only for 1С 8.3 in thick client under Windows 7 x64.

To perform the test, you must first log under your account into https://dev.twitter.com/ (at the top right there will be a button SignIn). Then, at the same place, at the top right you must move the mouse over the top of your logo and select “My applications”. Click “Create new application”.

Fill the required fields and receive two keys Consumer key and Consumer secret, then click the blue button and create two more keys Access token and Access token secret. Access level for them can be Read and write.

Enter the key into the form.

The button “Read” will load your timeline, last 20 messages. If you have just created a Twitter account and are not signed for anything, then there will not be 20 messages in timeline and the errors will occur.

The button “Tell” will post the text on Twitter.

There is no error check, the code is very raw, AS IS.

If there is any problem with the keys, the Twitter will return on of the following errors:

{"errors":[{"message":"Bad Authentication data","code":215}]}

{"errors":[{"message":"Invalid or expired token","code":89}]}

{"errors":[{"message":"Could not authenticate you","code":32}]}

etc.

Note that the processor is made for the normal (non-managed) interface!

File: TwitterEng.zip