webhooks and note deletionswebhook
Posted 02 January 2013 - 09:03 PM
After delete I get a webhook hit with query string: userId=<user id>&guid=<guid>&reason=update
I can do a noteStore.getNote to figure out if it was deleted but by then its too late to look up notebook id.
Posted 03 January 2013 - 07:11 PM
Posted 08 January 2013 - 04:16 PM
Your only option is to cache the note's notebook every time you receive an update / create notification.
For my project, that'd mean caching all of a user's note/notebook assocations up front (after initial oauth handshake) because a delete could be the first webhook hit involving a given note. I wanted to avoid duplicating Evernote's data mainly due to laziness but also lack of resources.
Has there been any consideration in splitting the "update" webhook out into more specific ones? Examples would be note deleted, note moved, tags added, tags removed, etc. While probably increasing complexity on EN's backend it would, in theory, reduce load on EN's web services because webhook clients are being told what happened instead of having to figure it out by querying.
The new webhooks could have data specific to them:
note moved - old notebook id, new notebook id
note deleted - old notebook id
tags added - tags that were added
tags removed - tags that were removed
This could be "EN webhooks v2.0" so clients using the current webhooks aren't broken.
Posted 08 January 2013 - 06:11 PM
Also tagged with one or more of these keywords: webhook
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users