@remit/api-openapi-types 0.0.31 → 0.0.33

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-openapi-types",
-  "version": "0.0.31",
+  "version": "0.0.33",
   "type": "module",
   "main": "types.d.ts",
   "types": "types.d.ts",

package/types.d.ts

@@ -329,6 +329,48 @@ a compile-time error rather than a value that silently sorts incorrectly.
       continuationToken?: String800;
       items: any[];
     }
+    /**
+     * An action was refused because the folder role it needs is not settled. The body is flat: `code`, `message` and `details` sit at the top level, which is what the API emits. Clients branch on `code` and word their prompt from `details`, never from `message`.
+
+`code: "folder_role_unresolved"` — no folder holds the role this action needs. `details` carries `role`, `accountId`, and `reason`, one of: `none` (the account has no candidate folder), `stale` (the folder the user appointed is gone from the mail server), `unconfirmed` (a folder matches by name, but neither the user nor the server's own flag ever said it holds the role).
+     */
+    export interface FolderRoleConflict {
+      statusCode: 409;
+      /**
+       * Error code
+       */
+      code: string;
+      /**
+       * Human-readable error message
+       */
+      message: string;
+      /**
+       * Additional error details
+       */
+      details?: Record;
+    }
+    /**
+     * The same flat 409 body as `FolderRoleConflict`, with one code only this endpoint can answer with.
+
+`code: "folder_role_unresolved"` — as everywhere else, with `details` carrying `role`, `accountId` and `reason`.
+
+`code: "mailbox_not_settled"` — the mailbox being appointed is still being created or deleted on the mail server, so it cannot yet hold a role. `details` carries `mailboxId` and `syncStatus`. Clearing a role is never refused this way.
+     */
+    export interface AppointFolderRoleConflict {
+      statusCode: 409;
+      /**
+       * Error code
+       */
+      code: string;
+      /**
+       * Human-readable error message
+       */
+      message: string;
+      /**
+       * Additional error details
+       */
+      details?: Record;
+    }
     export interface AmazonApiGatewayIntegration {
       type: "aws_proxy";
       httpMethod: "POST";
@@ -2762,6 +2804,25 @@ present only when `count=true`. Thread-specific so the shared `ResultList<T>`
        * SMTP server's Message-ID response (if different)
        */
       smtpMessageId?: string;
+      /**
+       * Whether the IMAP APPEND that files a copy in Sent has been confirmed, and
+the uid it produced. Written between the APPEND and the row delete that
+follows it, so a redelivered APPEND event skips straight to the delete
+instead of filing a second copy of the same message.
+
+Three readings, no absent one: the named sentinel `0` means no APPEND has
+been confirmed for this row. The named sentinel `-1` means an APPEND was
+confirmed but the server named no uid for it — UIDPLUS is an extension, and
+a server without it files the copy and reports nothing. Any positive value
+is the uid the server assigned. Only the latter two mean the copy exists, so
+a value neither of them reads as unfiled, which re-files at worst rather
+than dropping the row of a message that reached no folder.
+
+Deliberately not paired with a uidValidity: this never addresses the
+message, it only records that the copy exists. Everything that names a
+message forever (Message, Quarantine) stores both.
+       */
+      appendedUid: number;
       createdAt: number;
       updatedAt: number;
     }
@@ -4774,6 +4835,7 @@ declare namespace Paths {
     export type RequestBody = Components.Schemas.AppointFolderRoleInput;
     namespace Responses {
       export type $200 = void;
+      export type $409 = void;
     }
   }
   namespace ListFilters {
@@ -4903,6 +4965,7 @@ declare namespace Paths {
     }
     namespace Responses {
       export type $200 = void;
+      export type $409 = void;
     }
   }
   namespace TriggerSync {
@@ -5160,6 +5223,7 @@ declare namespace Paths {
     export type RequestBody = Components.Schemas.DeleteMessagesInput;
     namespace Responses {
       export type $200 = void;
+      export type $409 = void;
     }
   }
   namespace MoveMessages {
@@ -6325,6 +6389,8 @@ export type ValidationError = Components.Schemas.ValidationError;
 export type ApiError = Components.Schemas.ApiError;
 export type AccessPattern = Components.Schemas.AccessPattern;
 export type ResultList = Components.Schemas.ResultList;
+export type FolderRoleConflict = Components.Schemas.FolderRoleConflict;
+export type AppointFolderRoleConflict = Components.Schemas.AppointFolderRoleConflict;
 export type AmazonApiGatewayIntegration = Components.Schemas.AmazonApiGatewayIntegration;
 export type NotFoundError = Components.Schemas.NotFoundError;
 export type InternalServerError = Components.Schemas.InternalServerError;