The Microsoft Graph Explorer lets developers quickly navigate and test API endpoints.
The Graph Explorer is written in TypeScript and powered by:
npm installto install project dependencies.npmis installed by default with Node.js.npm startstarts the TypeScript compiler in watch mode and the local server. It should open your browser automatically with the Graph Explorer at http://localhost:3000/.
- You'll need to register an app on apps.dev.microsoft.com to configure the login page for your local Graph Explorer. Under
PlatformsclickAdd Platformand select Web.Allow Implicit Flowshould be checked and sethttp://localhost:3000as the redirect URL. You don't need a client secret since the explorer is a single page application. - Rename
secrets.sample.jstosecrets.jsin the project root and insert your client ID.
npm testto run tests from the command line for scenarios like parsing metadata and functional explorer tests.npm run import:loc-stringscombines all the loc files intranslation_files/toscripts/loc_strings.tsnpm run build:prodto build the minified explorer for production use.
Please see the contributing guidelines.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
We want the explorer to have rich samples for calling all APIs in the Microsoft Graph. If you have ideas for sample queries, you can edit sample-queries.csv and then run npm run import:samples. This will convert the samples in the CSV file to structured objects in src/app/gen-queries.ts.
Some sample queries have ids or other string constants that are different for authenticated users and the sample tenant. These tokens are maintained in tokens.ts and more documentation for them can be found in base.ts.
When you send a pull request, please commit both the sample-queries.csv and the src/app/gen-queries.ts file. We will then review your sample queries, and ensure our demo tenant has some sample data for that query.
Permissions like Mail.Read are listed in scopes.ts and each permission has a few properties, like its name and description.
{
name: "Calendars.ReadWrite",
description: "Have full access to user calendars",
longDescription: "Allows the app to create, read, update, and delete events in user calendars.",
preview: false,
admin: false
}Edits to this file can be made directly from Github.com so you don't even have to clone the project to add a new permission. You can also see a merged pull request for adding the Reports.Read.All permission.
Copyright (c) 2017 Microsoft. All rights reserved.