Skip to content

Commit 67e45a5

Browse files
Update wording of top level error codes to be more prescriptive. (#463)
* Update GuidelinesGraph.md * Update graph/GuidelinesGraph.md Co-authored-by: Darrel <[email protected]> --------- Co-authored-by: Darrel <[email protected]>
1 parent 313753e commit 67e45a5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

graph/GuidelinesGraph.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,7 @@ Microsoft REST API Guidelines provide guidelines that Microsoft Graph APIs shoul
285285
}
286286
```
287287

288-
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:
288+
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:
289289

290290
- **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).
291291

0 commit comments

Comments
 (0)