|
1 | 1 | # Microsoft Graph REST API Guidelines
|
2 | 2 |
|
3 | 3 | Table of Contents
|
4 |
| - |
5 |
| -[[_TOC_]] |
| 4 | +- [Microsoft Graph REST API Guidelines](#microsoft-graph-rest-api-guidelines) |
| 5 | + - [](#) |
| 6 | + - [History](#history) |
| 7 | + - [Introduction](#introduction) |
| 8 | + - [Legend](#legend) |
| 9 | + - [Design Approach](#design-approach) |
| 10 | + - [Naming](#naming) |
| 11 | + - [Casing](#casing) |
| 12 | + - [Prefixes and Suffixes](#prefixes-and-suffixes) |
| 13 | + - [Uniform Resource Locators (URLs)](#uniform-resource-locators-urls) |
| 14 | + - [Category](#category) |
| 15 | + - [Query Support](#query-support) |
| 16 | + - [Recommended Modeling Patterns](#recommended-modeling-patterns) |
| 17 | + - [Behavior Modeling](#behavior-modeling) |
| 18 | + - [HTTP Operations](#http-operations) |
| 19 | + - [Microsoft Graph rules for modeling behavior](#microsoft-graph-rules-for-modeling-behavior) |
| 20 | + - [Error Handling](#error-handling) |
| 21 | + - [API contract and non-backward compatible changes](#api-contract-and-non-backward-compatible-changes) |
| 22 | + - [Versioning and Deprecation](#versioning-and-deprecation) |
| 23 | + - [Deprecation Process](#deprecation-process) |
| 24 | + - [Common API Patterns](#common-api-patterns) |
| 25 | + - [References](#references) |
6 | 26 |
|
7 | 27 | ##
|
8 | 28 | #### History
|
@@ -194,7 +214,7 @@ enterprise perspectives and represents one of the following:
|
194 | 214 | Top-level API categories are aligned with documentation, developer tools, and in
|
195 | 215 | general are relatively stable. If a new category needs to be created, it requires an API REview and an API Council approval.
|
196 | 216 |
|
197 |
| -#### Query |
| 217 | +### Query Support |
198 | 218 |
|
199 | 219 | Microsoft Graph APIs should support basic query options in conformance with
|
200 | 220 | OData specifications and [Microsoft REST API
|
@@ -275,7 +295,7 @@ its request/response bodies, establishes the overall contract that developers
|
275 | 295 | have with your service. As an API provider, how you manage the overall request /
|
276 | 296 | response pattern should be one of the first implementation decisions you make.
|
277 | 297 |
|
278 |
| -#### Microsoft Graph rules for modeling behavior: |
| 298 | +#### Microsoft Graph rules for modeling behavior |
279 | 299 |
|
280 | 300 | |Requirements |Severity|
|
281 | 301 | |----------------------------------------------|----------------------------------------------|
|
|
0 commit comments