The Community is undergoing a major upgrade. Find out more, ask us questions or share your thoughts here.
Forum Discussion
The Cursor of a user
Hello again. After some searching, I'm back with another question that mirrors this one (https://www.dropboxforum.com/t5/API-Support-Feedback/Webhook-to-get-the-latest-changes-for-each-user-in-the/t...
If the "entries" value is an empty list like you've shown here, it just means that there are no new entries to return for the cursor you supplied. (If the token or cursor were invalid, the API would respond with a specific error accordingly.)
Note that if you go through the /2/files/list_folder results and save the cursor after the webhook is received, there may not be any further results.
The basic flow typically looks like this:
- the user connects to the app for the first time
- the app starts listing the files and folders for the user using /2/files/list_folder and /2/files/list_folder/continue as necessary
- the app stores the last returned cursor
- the user leaves and some time passes
- the user makes changes elsewhere
- Dropbox sends the webhook notification for that user
- the app recieves the webhook notification for that user and looks like up the last received cursor for that user
- the app calls /2/files/list_folder/continue with that cursor to get the latest changes
So I had tried that and did it again. Saved the cursor and the _id after the webhook is recieved (thanks to list_folder) and then use the cursor with the list_folder/continue.
But the "entries" returnedwas empty
"entries": []
Does that mean the cursor isn't good ? The token ?
Anyway, I'll try again, differently. Thanks
Greg-DB
Dropbox Staff
Dropbox StaffIf the "entries" value is an empty list like you've shown here, it just means that there are no new entries to return for the cursor you supplied. (If the token or cursor were invalid, the API would respond with a specific error accordingly.)
Note that if you go through the /2/files/list_folder results and save the cursor after the webhook is received, there may not be any further results.
The basic flow typically looks like this:
- the user connects to the app for the first time
- the app starts listing the files and folders for the user using /2/files/list_folder and /2/files/list_folder/continue as necessary
- the app stores the last returned cursor
- the user leaves and some time passes
- the user makes changes elsewhere
- Dropbox sends the webhook notification for that user
- the app recieves the webhook notification for that user and looks like up the last received cursor for that user
- the app calls /2/files/list_folder/continue with that cursor to get the latest changes
