From fdc7acdb6869828245c096aadaeee42fda0d376f Mon Sep 17 00:00:00 2001 From: Lionel Ong Date: Mon, 30 Nov 2020 21:39:02 +1100 Subject: [PATCH] Added 409 status code when desired GUID conflicts --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index d8d024f..f9aa06e 100644 --- a/README.md +++ b/README.md @@ -17,6 +17,7 @@ * [1.3 Updating Resources via HTTP PUT](#13-updating-resources-via-http-put) * [1.4 Cross Origin Resource Sharing (CORS)](#14-cross-origin-resource-sharing-cors) * [1.5 Http Status Codes](#15-http-status-codes) + + [1.5.1 Conflict on creation](#151-conflict-on-creation) * [1.6 Error Response Body Format](#16-error-response-body-format) * [1.7 DateTime Format](#17-datetime-format) * [1.8 Additional Response and Request Object Properties](#18-additional-response-and-request-object-properties) @@ -102,6 +103,10 @@ Generally, these response codes shall be used in the API: `POST` and `PUT` requests do usually include the created/modified resource in the response body. Exceptions to this rule are described in the specific section for the resource. +### 1.5.1 Conflict on creation + +For resource creation by `POST` with optional GUID specified, if the GUID already exists in the target system, status code `409 - Conflict` will be returned. + ## 1.6 Error Response Body Format All OpenCDE APIs have a specified error response body format [error.json](schemas/error.json).