Server API Documentation

[heywoodlh]

First off, thanks for an amazing product.

Is there any generic documentation on the server API? I'm sure people (myself included) would love to write their own clients for WeMessage that wasn't limited to just Android.

[marchharesoftware]

I 'second' that. Documentation of the protool used between the 'device' and the 'server' would be awesome.

For anyone wanting to reverse engineer it, the main recieve loop (after device authenticaiton) is here.

The source code refers to the tokens receievd from the device (weMessage for Android) as 'object' - which is an overloaded word in English, so I dislike it. But I can completely understand why the author did that. Because tall the 'better' words are taken with other meanings already, eg:

• message, well that's the main type of object weServer handles
• command, that's the things you type in to the server window, eg: to change password
• etc.

So here is the list of 'objects' and their 'sub-objects' and 'sub-sub-objects' based on a quick read of the source code:

• Heartbeat
• EncryptedFile
• EncryptedText
  • CONNECTION_TERMINATED
  • REGISTRATION_TOKEN
  • NEW_MESSAGE
  • ACTION
    • ADD_PARTICIPANT
    • CREATE_GROUP
    • LEAVE_GROUP
    • RENAME_GROUP
    • REMOVE_PARTICIPANT
  • CONTACT_SYNC

Obvjously those 'objects' are common between the server and client, so of course the code is in 'commons/connection'.

And useful constants are here (of course).