![]() ![]() UPDATE: FileMaker 16 now includes the ability to set headers, which means a plugin is no longer required. Once you have your API information, you will need authenticate your solution with the Google Calendar API. Keep your client secret hidden from the world as the combination of the Client ID and Client Secret will be used to authorize your solution to make changes to the end user's calendar. Once the Client ID has been created, copy the Client ID and Client Secret into your solution. This is only used as a landing page for authentication and does not need to be anything special. You will also need to set the redirect URI to or any valid website that will not redirect to something else. ![]() We will be using HTTP requests, so you will want to mark that the API will be accessed via a web browser client and that you will be accessing user data. This will take you to a setup process where the API will be managed. ![]() ![]() Once you have created the project, you will then need to enable the Calendar API. The first step of this integration is to create a project in the Google Developers Console. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |