The Graph DevX API is a backend RESTful API that primarily exposes resources that are consumed by Microsoft Graph documentation, Graph Explorer, Powershell sdk and Graph samples workload teams which are managed by the Graph PM team. It serves up a list of the following resources:
- Sample Queries: A set of queries that you can run against Microsoft Graph.
- Permissions: a set of permissive scopes for running different queries on Graph Explorer for different APIs.
- OpenAPI Descriptions: OpenAPI definitions for APIs within MS Graph which are used by Graph Explorer and Powershell sdk.
- Changes: Changelog info for Microsoft Graph versions v1.0 and beta.
- Known Issues: A list of known issues for Graph and the statuses of the issues.
DevX API is a collection of the following endpoints for different services:
This endpoint provides a means of getting a code snippet on how to perform a certain action on Microsoft Graph. The API takes in the HTTP request message to be sent to Microsoft Graph and the programming language to return a response with the code snippet string. The API currently supports the generation of snippets to the Microsoft Graph API in the following languages:
- C#
- Javascript
- Java
- Go
- PowerShell
- TypeScript
- PHP
- Python
This endpoint serves up the list of sample queries queryable by their category name, human name or tip. Once they are checked in through the DevX Content Repo, DevX API fetches the samples and feeds them to Graph Explorer for users to run their queries.
This endpoint serves up a list of scopes and their information, ordered from the least to most permissive, when given a request url, an HTTP verb/method (GET, PUT, POST, DELETE) and the scope type (DelegatedWork, DelegatedPersonal or Application). Graph Explorer uses this endpoint to render the list of sample queries on the UI.
The Changes endpoint will be used primarily by Graph Explorer to surface changelog info. The changelog info describes Microsoft Graph API endpoint changes that have occurred in both V1.0 and Beta. Graph Explorer will call this Changelog endpoint to retrieve any changelog info. associated with a particular Microsoft Graph endpoint. Changelog info can be retrieved by:
- Microsoft Graph url
- Workload name
- Dates
- Number of days
- The response can also be paginated.
Surfaces a list of known issues with MS Graph from different workloads and teams, for better tracking and keeping the known issues upto date.
The OpenAPI endpoint takes in clean Graph metadata in csdl format and converts it to relevant Open API descriptions using the OpenAPI specification standard. Its is used by:
- Powershell sdk to generate modules and commands for making calls against Graph.
- Graph Explorer to populate the autocomplete component with available query param results when running sample queries.
-
Clone the repo into your local machine by running this command:
(git clone https://github.com/microsoftgraph/microsoft-graph-devx-api.git) -
Open the
solution file(.sln)in the root of the project with Visual Studio and set the GraphWebAPI as the launch project.
- Run the app:
https://localhost:44399/and call the different endpoints
This API makes use of Swagger UI to expose its resources for end user consumption. Some protected resources can be called only after a successful authentication with Azure AD.
Calling the secured resources of the API requires authentication with Azure AD.
- Navigate to: https://graphexplorerapi.azurewebsites.net/swagger/index.html and click on the Authorize button.
- In the dialog window that opens, select the scope checkbox.
- Choose Authorize.
- You will be redirected to a separate window where you will be asked to log in with your Microsoft account and asked to grant permission to Graph Explorer API Swagger UI. Choose Accept.
- Upon successful authorization, you will be redirected back to the Swagger UI window and you will see the below dialog. Choose Close.
-
Click the Try it out button to make a call to a resource.
-
Input your parameters and click on the Execute button to make the request.
-
Request responses will be displayed in the Responses window.
Our versioning schema is tied to our default date-based build version in our build pipeline whose format is (v$(Build.BuildNumber)-$(Build.BuildId))
- Download and Install Git to your machine https://git-scm.com/downloads
- Download and Install VS Code to your machine https://code.visualstudio.com/download
- Fork/Clone the repo into your local machine
- Create a new branch
- Make changes
- Create a PR against dev branch
For any security loophole, kindly report to https://aka.ms/report-security-issue
For open-source contribution guidelines documentation, take a lot at the following resources:
-
Contact: opencode@microsoft.com
Copyright (c) Microsoft Corporation. All Rights Reserved. Licensed under the MIT license.