integrations.allow

Redirect to the admin consent page for the given Integration. That will show a page where an admin of the external service must log in and agree to allow Relay to access that service. The Integration entity does not need to exist in Relay prior to sending this request, that is, you can call this method without first calling integrations.insert, as the Integration entity will be created in Relay once the callback from the third-party service is sent to Relay. To enable Microsoft Office 365 integration with Relay, call this API method in a browser, such as in a popup window (iframes are discouraged because many log in pages for identity providers like Microsoft or other SSO IDPs send a Content-Security-Policy or X-Frame-Options header that prevents the log in page from being loaded in a frame). Note that this Relay API method does require authentication. The easiest way to supply authentication for a popup window is to send the accesstoken query parameter. See authentication for examples of sending this query parameter. The administrator can then log in to the third-party service and accept the consent request. This will redirect back to a blank Relay page which will post a message to the window's opener with the message integration_auth_flow_done, so the opener can close the popup and perform any further actions it needs to, such as refreshing the Office 365 integration status using integrations.get. At this point, Relay will be able to fetch calendar events from Office 365 for Endpoints with the OFFICE_365 calendar type. Note that in addition to this step, an administrator must also follow the rest of steps in the Office 365 Calendar Setup guide to allow Relay to read the titles and descriptions of meetings.