How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microsoft Exchange Mailbox Discovery API

Operations for discovering mailbox structure and content

Microsoft Exchange Mailbox Discovery API is one of 20 APIs that Microsoft Exchange publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Mailbox Discovery. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, a changelog, and an API reference.

This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0-beta.

Requests are made against a single base URL, https://graph.microsoft.com/beta.

2 operations 2 paths 3 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0-beta
Base URL
https://graph.microsoft.com/v1.0
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Microsoft Exchange Mailbox Discovery API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 3 scopes. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 authorization with Microsoft identity platform

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Mailbox Discovery 2

Operations for discovering mailbox structure and content

GET
/users/{user-id}/mailboxes
Microsoft Exchange List mailboxes
listMailboxes 1 param → 200401403404
GET
/users/{user-id}/mailboxes/{mailbox-id}/folders
Microsoft Exchange List mailbox folders
listMailboxFolders 4 params → 200401403404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are MailboxFolder (7 properties), Mailbox (6 properties), ODataError (1 property). Each schema is shown below with its type and property counts.

ODataError
object
OData error response
1 property
Mailbox
object
Represents a user's mailbox
6 properties
MailboxFolder
object
A folder in a mailbox
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-exchange-mailbox-discovery-api-openapi.yml Raw ↑

Other APIs Microsoft Exchange publishes across the network.

Exchange Web Services (EWS)
Exchange Online PowerShell API
Exchange Autodiscover API
Microsoft Exchange Accepted Domains API
Microsoft Exchange Attachments API
Microsoft Exchange Calendars API
Microsoft Exchange Contact Folders API
Microsoft Exchange Contacts API
Microsoft Exchange Distribution Groups API
Microsoft Exchange Events API
Microsoft Exchange Mail Folders API
Microsoft Exchange Mailbox Export API
Where this information came from

This is an independent, third-party profile of Microsoft Exchange Mailbox Discovery API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.