@remit/api-openapi-spec 0.0.76 → 0.0.77

package/openapi.json

@@ -4881,7 +4881,17 @@
             }
           },
           "404": {
-            "description": "Nothing answers to this address, or the caller may not learn that something does. `code` is `not_found`.",
+            "description": "No message answers to this id, or the caller may not learn that one does.\n`code` is `not_found`, or `message_gone_from_server` when the mail server no\nlonger holds the message at its UID — another client expunged it or moved it\naway before its body was stored. That answer carries `details.messageId`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/ApiError"
+                }
+              }
+            }
+          },
+          "409": {
+            "description": "The same flat 409 body, for a message whose folder and uid do not name the same message.\n\n`code: \"message_placement_unsettled\"` — the message is mid-move, so its row names the destination folder while its uid still belongs to the source; acting on that pair would hit whatever the destination holds at that uid. `details` carries `accountId`, `messageId` and `reason`, one of: `in_flight` (the move is still running, and the same request succeeds once it confirms) or `unverified` (the move gave up without confirming, so where the message sits is unknown until the folder is resynced).",
             "content": {
               "application/json": {
                 "schema": {
@@ -5113,7 +5123,17 @@
             }
           },
           "404": {
-            "description": "Nothing answers to this address, or the caller may not learn that something does. `code` is `not_found`.",
+            "description": "No message answers to this id, or the caller may not learn that one does.\n`code` is `not_found`, or `message_gone_from_server` when the mail server no\nlonger holds the message at its UID — another client expunged it or moved it\naway before its body was stored. That answer carries `details.messageId`.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/ApiError"
+                }
+              }
+            }
+          },
+          "409": {
+            "description": "The same flat 409 body, for a message whose folder and uid do not name the same message.\n\n`code: \"message_placement_unsettled\"` — the message is mid-move, so its row names the destination folder while its uid still belongs to the source; acting on that pair would hit whatever the destination holds at that uid. `details` carries `accountId`, `messageId` and `reason`, one of: `in_flight` (the move is still running, and the same request succeeds once it confirms) or `unverified` (the move gave up without confirming, so where the message sits is unknown until the folder is resynced).",
             "content": {
               "application/json": {
                 "schema": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-openapi-spec",
-  "version": "0.0.76",
+  "version": "0.0.77",
   "description": "Remit API OpenAPI 3 document, generated from TypeSpec.",
   "exports": {
     ".": "./openapi.json",