{"id":6478,"date":"2021-06-23T10:19:06","date_gmt":"2021-06-23T18:19:06","guid":{"rendered":"https:\/\/officedevblogs.wpengine.com\/?p=6478"},"modified":"2022-05-26T14:38:51","modified_gmt":"2022-05-26T21:38:51","slug":"explore-microsoft-graph-with-postman","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/explore-microsoft-graph-with-postman\/","title":{"rendered":"Microsoft Graph Mailbag – Explore Microsoft Graph with Postman"},"content":{"rendered":"

In today\u2019s Microsoft Graph Mailbag post, we\u2019ll take a look at the Microsoft Graph Postman collection<\/a>.<\/p>\n

\"Microsoft<\/p>\n

Please be sure to follow this blog series using\u202fhttps:\/\/aka.ms\/MSGraphMailbag<\/a>\u202for with RSS using\u202fhttps:\/\/developer.microsoft.com\/graph\/blogs\/feed\/?tag=MSGraphMailbag<\/a>.<\/p>\n

Introduction<\/h2>\n

The Microsoft Graph Postman collection is a curated set of API requests that you can use to experiment with and explore the Microsoft Graph API. It serves a similar purpose as the Graph Explorer<\/a>, with a few notable differences. With the Postman collection, you can save custom requests and make requests with an app-only token<\/a>.<\/p>\n

Getting started<\/h2>\n

Instructions on forking and configuring the collection are found in Use Postman with the Microsoft Graph API<\/a>. Jeremy Thake has posted a short YouTube video<\/a> on getting started. I\u2019ll summarize the process here.<\/p>\n

Fork the collection<\/h3>\n

Forking the collection<\/a> is necessary to get your own copy of the collection that you can modify. Once you’ve forked the collection into your personal workspace, you can use it in your browser or using the Postman desktop application.<\/p>\n

Configure authentication<\/h3>\n

Postman has support for OAuth2 built in. The requests in our collection have been pre-configured to use the appropriate OAuth2 flows. Requests in the\u00a0Delegated\u00a0<\/strong>folder use the authentication code flow to authenticate as a user. Requests in the\u00a0Application<\/strong> folder use the client credentials flow to authenticate as an application. Keep in mind that in order to use the requests in the Application <\/strong>folder, you will need an administrator to consent to the application permissions.<\/p>\n

As you explore the requests in the collection, you’ll need to add additional permissions to your application registration and request a new token. For example, if you followed along with the instructions in our documentation, your application registration currently has User.Read<\/code> and Mail.Read<\/code> delegated permissions, and User.Read.All<\/code> application permissions. That means the\u00a0Get my messages\u00a0<\/strong>request will succeed, but the\u00a0Get my calendars<\/strong> request will fail with 403 Forbidden<\/code>. To complete the request successfully, add Calendars.Read<\/code> to the\u00a0API permissions\u00a0<\/strong>on the application registration, grant admin consent, and get a new token<\/a> in Postman.<\/p>\n

Add a request<\/h3>\n

Once you’ve explored the requests included in the collection, you may want to add additional requests. For example, there are no request for the personal contacts APIs. Let’s walk through the process of adding a request to list the authenticated user’s contacts.<\/p>\n

First, add a\u00a0Personal contacts\u00a0<\/strong>folder in the\u00a0Delegated\u00a0<\/strong>folder. Select the ellipsis (\u2026) on the\u00a0Delegated\u00a0<\/strong>folder to open the action menu, and select\u00a0Add Folder<\/strong>. Be sure to leave the\u00a0Type\u00a0<\/strong>field set to\u00a0Inherit auth from parent<\/strong>.<\/p>\n

\"A<\/p>\n

Add a request to the\u00a0Personal contacts\u00a0<\/strong>folder named\u00a0Get my contacts<\/strong>. Using the information from the list contacts API reference page<\/a>, we can fill in the request.<\/p>\n