Event

Event can be one of:

Method	Description
reset	client should reset it's state to empty root directory
createfolder	folder is created, metadata is provided
deletefolder	folder is deleted, metadata is provided
modifyfolder	folder is modified, metadata is provided
createfile	file is created, metadata is provided
modifyfile	file data is modified, metadata is provided (normally modifytime, size and hash are changed)
deletefile	file is deleted, metadata is provided
requestsharein	incoming share, share is provided
acceptedsharein	you have accepted a share request (potentially on another device), useful to decrement the counter of pending requests. share is provided. It is guaranteed that you receive createfolder for the folderid (and all the contents of the folder) of the share before you receive acceptedshare, so it is safe to assume that you will be able to find folderid in the local state.
declinedsharein	you have declined a share request, share is provided (this is delivered to the declining user, not to the sending one)
declinedshareout	same as above, but delivered to the user that is sharing the folder.
cancelledsharein	the sender of a share request cancelled the share request
removedsharein	your incoming share is removed (either by you or the other user)
modifiedsharein	your incoming share in is modified (permissions changed)
modifyuserinfo	user's information is modified, includes userinfo object with the following fields: userid premium premiumexpires (if premium is true) language email emailverified quota usedquota. Every user is guaranteed to have one such event in it's full state diff.

Pay close attention to deletedfileid field set in metadata returned from either modifyfile or createfile when one file is atomically replaced with another one

Clients are advised to ignore events that they don't understand (as opposed to issuing errors). For shares, a share object is provided.