![]() It is a simple matter of substituting the string “/user//mailFolders see lines 39-44 where we read it from the preferences and then manipulate it for our service/user scenario The only difference between the two routes is the same between all endpoints. In FileMaker, we store the ‘/users’ route in our preferences table: Figure 30. We can use the “/users/” route when we do server-to-server integrations and potentially need to repeat this call for a set of different users. The “/me/” route should be used in the scenarios where we used the interactive user login. For instance, to get a list of mail folders for a user, we should use a GET call to one of these two endpoints. The API documentation specifies which endpoint you should use it also tells you what HTTP verb to use. ![]() The base URL for each call to the API is always the same, and each API function has its own endpoint (also sometimes called ‘route’). For OneDrive, we can get a list of all files and folders, download the actual file, upload a new file or create a new folder and we can ask the API to convert documents stored on OneDrive to PDF. We can retrieve a list of email accounts, mail folders per email accounts, emails for each mail folder, attachments for the emails we can reply in HTML to emails and attach multiple attachments. Using the API functionalityĪfter following the steps I provided in part one, we can use the API functionality to which we have given our Azure AD app permissions. Here in part two, I provide insights on using the Microsoft Graph API functionality in your FileMaker solution. ![]() In part one, I share the demise of basic authentication and why relying on strictly passwords is no longer a viable or safe option. ![]() Welcome to part two of a blog series on Microsoft’s Graph API for Office 365 in FileMaker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |