Azərbaycan dili Bahasa Indonesia Bosanski Català Čeština Dansk Deutsch Eesti English Español Français Galego Hrvatski Italiano Latviešu Lietuvių Magyar Malti Mакедонски Nederlands Norsk Polski Português Português BR Românã Slovenčina Srpski Suomi Svenska Tiếng Việt Türkçe Ελληνικά Български Русский Українська Հայերեն ქართული ენა 中文
Subpage under development, new version coming soon!

Subject: API Information and Usage

  • 1
2017-07-24 19:15:19
I've been tinkering with the existing API (http://sokker.org/xmlinfo.php) and was hoping to get some additional information in regard to making my companion interface accessible to other SK members...

#1 - If I build a web-based companion interface and allow other SK members to use it, my web server will be making calls to the API on their behalf. Will that transaction make it appear as though everyone using my companion app is the "same user" logging into multiple accounts? I know there are other companion applications that run from individual desktops - which would not create this issue... but since the API will be called from my web server, I don't know how that would be handled - and I don't want anyone to be flagged as having multiple accounts just because they use my companion app.

#2 - Are there any new endpoints that are not listed in the documentation? I've noticed that the API document hasn't been updated in quite some time and I was just hoping more endpoints have been created.

(I'm sure I'll have more questions as these get answered - hopefully)

Thanks for your help!!
2017-11-17 09:42:32
hum a little late but i this can help.

#1 As rules says (point 16) the Sokker developers and admins can take sanctions for " program or scripts is determined to be detrimental to the game"... it all depends on their own judgment. Nothing is clear about what you can do or not.

But since there is no active admin/dev for years in this game i think you can use your account for api for years with no troubles :)
A better "secure" way is to ask and use the own log/pwd session for each users/api calls.

#2 Nothing more to my knowledge. Like point #1 no active dev for years mean no api changes for years.
  • 1