Webhooks notifications

1. The accounts array tells you which accounts have changes. Each "dbid:" string is account-specific. It's the account ID for a particular account, as used by API v2, e.g., as returned by /2/users/get_current_account.

2. The integer user ID format is used by API v1, and the "dbid:" format is used by API v2. So, if your app is built on API v1, you would check the delta.users value to determine which users have had changes. If your app is built on API v2, you would check list_folder.accounts. The intent is that your app would then call the relevant API endpoint to get information on the changes, e.g., /1/delta for API v1, or /2/sharing/list_folders/continue for API v2.

3. In order to make an API call for a particular user account, you need to have an access token for that account. Your app receives an access token for an account when the user authorizes the app to access their account. Your app should then store those access tokens for future use. In your case, you're only connecting to a single account (your own) so you'll only have one access token anyway.

4. The process_user method in the sample uses the account ID to look up the corresponding access token. That sample uses API v2, so it only needs the account ID format ("dbid:"), not the user ID format.