🎮 Graph API Explorer Lite
An interactive, no-auth sandbox to explore popular Microsoft Graph API endpoints. Instantly view required permissions and realistic mock JSON responses.
Endpoint Details
Get the profile of the currently authenticated user.
Required Permissions
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#users/$entity",
"businessPhones": [
"+1 412 555 0109"
],
"displayName": "Megan Bowen",
"givenName": "Megan",
"jobTitle": "Auditor",
"mail": "MeganB@contoso.OnMicrosoft.com",
"mobilePhone": null,
"officeLocation": "12/1110",
"preferredLanguage": "en-US",
"surname": "Bowen",
"userPrincipalName": "MeganB@contoso.onmicrosoft.com",
"id": "48d31887-5fad-4d73-a9f5-3c356e68a038"
}What is in this sandbox
The explorer is a static reference, not a live client: nothing is sent to Microsoft Graph and no sign-in is needed. It holds 22 commonly used v1.0 endpoints. For each one you get the HTTP method and URL, the delegated and application permissions Microsoft lists for it, and a mock JSON response shaped like the real payload so you can see which properties come back before you write any code. Type part of a path into the search box to filter the list.
Endpoints by area
- Users: GET /me, GET /me/manager, GET /me/memberOf, GET /users/{id}/photo/$value
- Groups & Teams: GET /groups, GET /teams/{team-id}/channels
- SharePoint & Sites: GET /sites/root, GET /sites/{site-id}/lists
- OneDrive: GET /me/drive, GET /me/drive/recent
- Mail & Calendar: GET /me/messages, GET /me/events
- Groups: GET /groups/{id}/members
- Teams: POST /teams/{team-id}/channels/{channel-id}/messages
- Files: GET /sites/{site-id}/drive/root/children, PUT /drives/{drive-id}/items/{parent-id}:/{filename}:/content, GET /me/drive/root/delta
- SharePoint: POST /sites/{site-id}/lists/{list-id}/items
- Batching: POST /$batch
- Change notifications: POST /subscriptions
- Search: POST /search/query
- Reports: GET /auditLogs/signIns
The mock responses use Microsoft's demo tenant data (the Contoso sample users), so IDs and values are illustrative. Permission names are the ones required at the time the list was written; check the Graph permissions reference before requesting them in an app registration, because Microsoft adds and renames scopes over time.
Frequently Asked Questions
No! This is a "Lite" mock version designed for quick reference without authenticating or setting up an Azure AD app. Browse endpoints, view required permissions, and see realistic JSON responses instantly.
They are realistic mock responses modeled exactly after the official Microsoft Graph API v1.0 documentation. The data structure, property names, and response format match what you'd get from a real API call.
Delegated permissions act on behalf of a signed-in user — the app can only access what the user can access. Application permissions act as a background service with tenant-wide access. Application permissions are more powerful but require admin consent.
Microsoft Graph is the unified API gateway to all Microsoft 365 services. A single endpoint (https://graph.microsoft.com) provides access to users, mail, calendar, files (OneDrive/SharePoint), Teams, Planner, and 40+ other services.
Go to Azure AD → App registrations → New registration. Set a redirect URI, then go to API permissions → Add a permission → Microsoft Graph. Select the required permissions (Delegated or Application) and grant admin consent if needed.
The most popular endpoints: /me (current user), /users (all users), /me/messages (emails), /me/events (calendar), /groups (M365 Groups/Teams), /sites/{id}/lists (SharePoint), and /me/drive/root/children (OneDrive files).
Graph returns a @odata.nextLink URL when there are more results. Keep making GET requests to the nextLink URL until it's no longer present. Default page size varies (10-100 items). Use $top to control page size, max is usually 999.