You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/restful-technical-profile.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ manager: celestedg
9
9
ms.service: active-directory
10
10
ms.workload: identity
11
11
ms.topic: reference
12
-
ms.date: 03/03/2020
12
+
ms.date: 03/16/2020
13
13
ms.author: mimart
14
14
ms.subservice: B2C
15
15
---
@@ -215,19 +215,7 @@ If the type of authentication is set to `Bearer`, the **CryptographicKeys** elem
215
215
216
216
## Returning error message
217
217
218
-
Your REST API may need to return an error message, such as 'The user was not found in the CRM system'. If an error occurs, the REST API should return an HTTP 409 error message (Conflict response status code) with following attributes:
219
-
220
-
| Attribute | Required | Description |
221
-
| --------- | -------- | ----------- |
222
-
| version | Yes | 1.0.0 |
223
-
| status | Yes | 409 |
224
-
| code | No | An error code from the RESTful endpoint provider, which is displayed when `DebugMode` is enabled. |
225
-
| requestId | No | A request identifier from the RESTful endpoint provider, which is displayed when `DebugMode` is enabled. |
226
-
| userMessage | Yes | An error message that is shown to the user. |
227
-
| developerMessage | No | The verbose description of the problem and how to fix it, which is displayed when `DebugMode` is enabled. |
228
-
| moreInfo | No | A URI that points to additional information, which is displayed when `DebugMode` is enabled. |
229
-
230
-
The following example shows a REST API that returns an error message formatted in JSON:
218
+
Your REST API may need to return an error message, such as 'The user was not found in the CRM system'. If an error occurs, the REST API should return an HTTP 4xx error message, such as, 400 (bad request), or 409 (conflict) response status code. The response body contains error message formatted in JSON:
231
219
232
220
```JSON
233
221
{
@@ -241,6 +229,17 @@ The following example shows a REST API that returns an error message formatted i
241
229
}
242
230
```
243
231
232
+
| Attribute | Required | Description |
233
+
| --------- | -------- | ----------- |
234
+
| version | Yes | Your REST API version. For example: 1.0.1 |
235
+
| status | Yes | Must be 409 |
236
+
| code | No | An error code from the RESTful endpoint provider, which is displayed when `DebugMode` is enabled. |
237
+
| requestId | No | A request identifier from the RESTful endpoint provider, which is displayed when `DebugMode` is enabled. |
238
+
| userMessage | Yes | An error message that is shown to the user. |
239
+
| developerMessage | No | The verbose description of the problem and how to fix it, which is displayed when `DebugMode` is enabled. |
240
+
| moreInfo | No | A URI that points to additional information, which is displayed when `DebugMode` is enabled. |
241
+
242
+
244
243
The following example shows a C# class that returns an error message:
0 commit comments