![]() Suggested notebook names must follow the same restrictions as standard Evernote notebook names as outlined in in the API reference documentation here. If there is no notebook in the user's account with the name you suggest through OAuth, a notebook with the suggested name will be created in the users account. If the user already has a notebook in their account with the name you suggest, that notebook will be selected. Where "Suggested Notebook Name" is the URL encoded name you would like to suggest to the user. & supportLinkedSandbox=true &suggestedNotebookName=Suggested%20Notebook%20Name Set supportLinkedSandbox to true and suggestedNotebookName to the URL encoded name you would like to suggest to the user. To suggest a notebook name to the user, add supportLinkedSandbox and suggestedNotebookName to your OAuth parameters. By default, a new notebook will be created in the user’s account called. The primary difference now is that users will be presented with the option to choose the notebook used by the application requesting authorization. Historically, the authentication screen notified the user that a given application would have access to their account for one year and which specific permissions the application would have (create notes, update notes, etc.). User FlowĪs with the OAuth process, the user authentication flow will remain largely the same. See the “Introduction to OAuth” section of our Authentication documentation for more information. Then get the GUID of the new notebook via listNotebooksĪs with legacy authentication to an entire user’s account, third-party developers should also build their application to elegantly handle the situation in which the authentication token expires or is revoked by the user. Rerun authentication process so the user can choose a new notebook Our recommendation is to alert the user as to what happened and prompt them to re-authorize your application, allowing them to select a different notebook. Your application should be prepared to handle this situation. ![]() In such a case, NoteStore.listNotebooks and NoteStore.listLinkedNotebooks will return empty result sets and NoteStore.getNotebook will result in an EDAMNotFoundException. It is possible that the user may delete the notebook to which your application has access. Otherwise the sandbox_lnb is set to false by default Error Handling When a user selects a shared or business notebook as the notebook for use with your application, the OAuth callback will have the sandbox_lnb parameter set to true. &preferRegistration=true& supportLinkedSandbox=true ![]() To include existing linked or business notebooks as options from which the user can choose their destination notebook, include supportLinkedSandbox=true in the OAuth URL during the authentication process:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |