Hi @jheasley
I did something similar on my .net core application last year.
To start with, Graph explorer is your best friend when it comes to learning exploring the APIs.
The shared meeting room calendar is tricky matter, and requires delegated access. From top of my head (I need to check as its been a while) you need the calendar view endpoint as user having resource delegated access to that mailbox.
https://graph.microsoft.com/beta/users/[YOUR-METING-ROOM-EMAIL]/calendarView
PS: I remember we didn't get the meeting subject/name - were only provided the person who booked via the API. Also to get all the meeting rooms I had to use the `findrooms` endpoint with some limitations on that end too.
As for that shared mailboxes, you can get that information for the signed in user (personal or any shared mailbox for that user). https://docs.microsoft.com/en-us/graph/api/resources/mail-api-overview?view=graph-rest-1.0
For authentication, see - https://docs.microsoft.com/en-us/graph/auth/auth-concepts
To use this in Qlik with REST connector, you can use the outh2 service app authentication flow. You will need to grant the application required permissions. You will then need to generate access token from Qlik Sense script each time you call the API. This is an example code for generating access token from Qlik - (this is from my github, I use very similar approach for google as well)
//---------------------------------------------------------------------------------------------------------------------
// This is calling the API using the refresh key granted to the application to gain a valid access token.
//---------------------------------------------------------------------------------------------------------------------
//Token exipiration time - Setting this in the past so the first run, it renews before code execution
LET vLoadTokenExpireTime = TIMESTAMP(NOW()-1000) ;
//Call this sub routine before all your other calls to make sure you have a valid token to complete the action
SUB renewToken(vLoadCallPlaceholder) //vLoadCallPlaceholder is a placeholder for future extensiblities
//Call Method
SET v.Load.Call.Method = 'POST'; //Change this to meet your need. This is for QV not for Sense
//Setting up client Id, client ecret and the refresh token veriables
SET vLoadClientId = '[YOUR REGISTERED CLIENT ID]';
SET vLoadClientSecret = '[YOUR REGISTERED CLIENT SECRET]';
SET vLoadResource = 'https://graph.microsoft.com/';
TRACE ===== Checking token expiration time =====;
IF vLoadTokenExpireTime <= NOW() THEN
TRACE ===== Token expired, initiating API call to revoke a new token =====;
LET vLoadRestPostPayLoad ='';
LET vLoadRestPostPayLoad = vLoadRestPostPayLoad & '&client_id=' & '$(vLoadClientId)';
LET vLoadRestPostPayLoad = vLoadRestPostPayLoad & '&resource=' & '$(vLoadResource)';
LET vLoadRestPostPayLoad = vLoadRestPostPayLoad & '&grant_type=client_credentials';
LET vLoadRestPostPayLoad = vLoadRestPostPayLoad & '&client_secret=' & '$(vLoadClientSecret)';
TRACE ====== Establishing Connection to API ======;
LIB CONNECT TO 'REST_POST'; //point this to your existing place holder REST connection
TRACE ====== Connection Success ======;
REM
Below we are using the "WITH CONNECTION" to overwrite the URL we established the initial connection with.
This allows us to add call parameters, headers for GET calls, for POST we can also add body (payload). You
can also structure your URL using content type and upload JSON or xml file or even test file, you should
use this to handle the pagination if the API supports pagination;
TRACE ====== Renewing Token ======;
Token:
SQL
SELECT
"access_token",
"token_type",
"expires_in"
FROM JSON (wrap on) "root"
WITH CONNECTION (
URL "https://login.microsoftonline.com/[YOUR TENANT]/oauth2/token",
HTTPHEADER "Content-Type" "application/x-www-form-urlencoded",
BODY "$(vLoadRestPostPayLoad)"
);
LET vLoadApiAccessToken = PEEK('access_token',0,'Token');
LET vLoadApiAccessTokenExpires = PEEK('expires_in',0,'Token');
LET vLoadTokenExpireTime = TIMESTAMP(NOW() + $(vLoadApiAccessTokenExpires)/86400);
TRACE ====== Token aquired ======;
DROP TABLE Token;
ELSE
TRACE ====== Token is still valid ======;
ENDIF;
END SUB;
//First call the Sub routine
CALL renewToken('1');
Hope this helps. I can look at the actual endpoint and how I managed all of it in our solution next time I get on my work laptop.
Regards
Kabir
Kabir
Please do not forget to the mark the post if you find it useful or provides you the solutions 🙂
.png "Luminary Alumni"){kind=icon}
