Skip to content

Commit 463ccb2

Browse files
authored
Update restful-technical-profile.md
Changing the status from 409 to 4xx
1 parent 868f764 commit 463ccb2

File tree

1 file changed

+13
-14
lines changed

1 file changed

+13
-14
lines changed

articles/active-directory-b2c/restful-technical-profile.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 03/03/2020
12+
ms.date: 03/16/2020
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
---
@@ -215,19 +215,7 @@ If the type of authentication is set to `Bearer`, the **CryptographicKeys** elem
215215

216216
## Returning error message
217217

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:
231219

232220
```JSON
233221
{
@@ -241,6 +229,17 @@ The following example shows a REST API that returns an error message formatted i
241229
}
242230
```
243231

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+
244243
The following example shows a C# class that returns an error message:
245244

246245
```csharp

0 commit comments

Comments
 (0)