From 67e45a5452b9b9f603b37c7f1318c9cfacf053a1 Mon Sep 17 00:00:00 2001 From: Gareth Jones Date: Fri, 30 Jun 2023 14:53:30 -0700 Subject: [PATCH] Update wording of top level error codes to be more prescriptive. (#463) * Update GuidelinesGraph.md * Update graph/GuidelinesGraph.md Co-authored-by: Darrel --------- Co-authored-by: Darrel --- graph/GuidelinesGraph.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/graph/GuidelinesGraph.md b/graph/GuidelinesGraph.md index 02203adb..e0fecabd 100644 --- a/graph/GuidelinesGraph.md +++ b/graph/GuidelinesGraph.md @@ -285,7 +285,7 @@ Microsoft REST API Guidelines provide guidelines that Microsoft Graph APIs shoul } ``` -The top-level error code must be aligned with HTTP response status codes according to [rfc7231 (ietf.org)](https://datatracker.ietf.org/doc/html/rfc7231#section-6). The following examples demonstrate error modeling for common use cases: +The top-level error code must match the HTTP response status code description, converted to camelCase, as listed in the [Status Code Registry (iana.org)](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml). The following examples demonstrate error modeling for common use cases: - **Simple error**: An API wants to report an error with top-level details only. The error object contains the top-level error code, message and target (optional).