@remit/api-openapi-types 0.0.39 → 0.0.41

package/package.json

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

package/types.d.ts

@@ -64,7 +64,7 @@ writer can reach is a vocabulary that lies about what the field means.
     /**
      * IMAP connection states per RFC 9051 Section 3
      */
-    export type ConnectionState = "not_authenticated" | "authenticated" | "selected" | "logout" | "reauth_required";
+    export type ConnectionState = "not_authenticated" | "authenticated" | "selected" | "logout" | "reauth_required" | "credentials_missing";
     /**
      * Phase of the initial account sync lifecycle
      */
@@ -73,6 +73,14 @@ writer can reach is a vocabulary that lies about what the field means.
      * Where a resolved FolderAppointment came from. Total and required: every role carries one, so a surface can tell a folder somebody chose from a folder reader guessed without inferring it from which fields happen to be present.
      */
     export type FolderAppointmentSource = "Appointed" | "Flagged" | "Reserved" | "Proposed" | "Stale" | "None";
+    /**
+     * Whether an import writes. The default is the dry run, so the wizard can show what a file would do before anything lands.
+     */
+    export type ConfigImportMode = "validate" | "apply";
+    /**
+     * What an import does when the configuration it is importing into is not empty.
+     */
+    export type ConfigImportOnExisting = "abort" | "merge";
     /**
      * Outcome of the most recent manifest check. `ok` when a manifest was fetched and validated, `failed` when it could not be, `disabled` when no manifest URL is configured or no check has ever run (RFC 037 D8).
      */
@@ -249,6 +257,38 @@ distinguishable from a network failure without parsing prose.
      * Known user-setting keys. Each maps, in the registry, to a required value kind and a zod schema. New keys are added deliberately by extending this enum and the registry — never as an ad-hoc column.
      */
     export type AccountSettingName = "Theme" | "Density" | "DefaultComposerFormat" | "PinnedFolders" | "AccountSignaturePlainText" | "AccountSignatureHtml" | "AccountDisplayName" | "AccountMuted" | "AccountComposeLanguages" | "MailboxDisplayName" | "MailboxMuted" | "FolderRoleAppointment" | "FolderRoleAppointmentLabel" | "MailboxRole";
+    /**
+     * Lifecycle of one applied configuration import. An import is Complete the moment every folder reference in the file has been bound to a real mailbox; until then it is Pending, waiting on the IMAP discovery that will produce those mailboxes.
+     */
+    export type ConfigImportState = "Pending" | "Complete";
+    /**
+     * Which piece of configuration a still-unbound folder reference belongs to. A mailbox id is regenerated by every discovery, so an imported file names folders by IMAP path and the binder writes the row once a path resolves.
+     */
+    export type ConfigImportRefKind = "FolderRole" | "MailboxOverride" | "FilterAction";
+    /**
+     * Display color for a calendar collection. Positional rather than named: the palette is a client-side concern, so the store carries the slot and the client owns what it renders (issue #15).
+     */
+    export type CalendarColor = "Cal1" | "Cal2" | "Cal3" | "Cal4" | "Cal5" | "Cal6";
+    /**
+     * Which iCalendar components a collection accepts (RFC 4791 supported-calendar-component-set). Only VEVENT is stored today; VTODO and VJOURNAL collections would be separate members, so the value is a property of the collection rather than of each object.
+     */
+    export type CalendarComponentSet = "VeventOnly";
+    /**
+     * Where a calendar collection came from. `Default` is the one provisioned per account config on first use and is never deleted; `UserCreated` is one a person made; `MailDerived` is one populated from mail rather than by a person.
+     */
+    export type CalendarSource = "Default" | "UserCreated" | "MailDerived";
+    /**
+     * Projection of a VEVENT's STATUS property (RFC 5545 3.8.1.11). A VEVENT with no STATUS projects as `Confirmed`, which is the value RFC 5545 gives an event whose status is unstated.
+     */
+    export type CalendarEventStatus = "Confirmed" | "Tentative" | "Cancelled";
+    /**
+     * Projection of a VEVENT's TRANSP property (RFC 5545 3.8.2.7) — whether the event consumes free/busy time. A VEVENT with no TRANSP projects as `Opaque`, the RFC default.
+     */
+    export type CalendarTransparency = "Opaque" | "Transparent";
+    /**
+     * How confidently a stored time was placed on the clock. A calendar that cannot say this hides its worst failure: an event read in the wrong zone is off by hours and looks exactly like an event read correctly.
+     */
+    export type ZoneCertainty = "Local" | "Explicit" | "Ambiguous";
     /**
      * Explicit state engine for a pending placement-move marker (issue #1271, epic #1281). Recovery keys off this field, not control-flow inference: a redelivered/retried call drives a marker forward from whichever state it is actually in, rather than re-deriving intent by comparing the message's current location.
      */
@@ -860,6 +900,10 @@ never from a raw content-type line — parameters carry `name=` and
        * Associated email accounts
        */
       accounts: AccountResponse[];
+      /**
+       * Absent unless a configuration import is still waiting on folders IMAP has not produced yet (#1021). Nothing polls a separate route for it.
+       */
+      pendingImport?: PendingConfigImport;
     }
     /**
      * Configuration container for user accounts. Groups multiple IMAP accounts under a single user.
@@ -1233,6 +1277,23 @@ never from a raw content-type line — parameters carry `name=` and
        */
       staleAppointmentPath?: String512;
     }
+    /**
+     * An import that is still waiting for IMAP discovery to produce the folders its
+file named. The folder appointed to a role, a folder's own display name or
+mute, and a filter's move destination are all bound by path; a path this
+account does not hold yet is kept, not guessed, and bound the moment discovery
+finds it.
+     */
+    export interface PendingConfigImport {
+      /**
+       * The import still waiting
+       */
+      importId: UUID;
+      /**
+       * The IMAP paths no mailbox answers to yet, deduplicated
+       */
+      folderPaths: string[];
+    }
     /**
      * A configuration export: one versioned document carrying every user decision this instance holds, and no credential.
      */
@@ -1246,6 +1307,104 @@ never from a raw content-type line — parameters carry `name=` and
        */
       document: Record;
     }
+    /**
+     * Request body for POST /config/import
+     */
+    export interface ImportConfigInput {
+      /**
+       * `validate` writes nothing; `apply` writes.
+       */
+      mode?: ConfigImportMode;
+      /**
+       * What to do when this configuration is not empty.
+       */
+      onExisting?: ConfigImportOnExisting;
+      /**
+       * The config document, as exported.
+       */
+      document: Record;
+    }
+    /**
+     * The outcome of a validate or an apply. A rejected document is an answer, not a failure: `valid` is false and `errors` says why.
+     */
+    export interface ConfigImportReport {
+      /**
+       * Import identity; present on apply, so the folder bindings this import is still waiting on can be named later
+       */
+      importId?: UUID;
+      /**
+       * Whether the document is importable at all
+       */
+      valid: boolean;
+      /**
+       * Schema version of the submitted document
+       */
+      schemaVersion: number;
+      /**
+       * Whether anything was written
+       */
+      applied: boolean;
+      /**
+       * Per-item verdicts
+       */
+      items: ConfigImportItemReport[];
+      /**
+       * Blocking problems; non-empty means nothing was written
+       */
+      errors: ApiError[];
+      /**
+       * Non-blocking notes - e.g. a folder path this account does not hold yet
+       */
+      warnings: ApiError[];
+      /**
+       * Accounts that landed needing a credential before they can sync
+       */
+      accountsNeedingCredentials: UUID[];
+    }
+    /**
+     * What became of one item in the submitted document
+     */
+    export interface ConfigImportItemReport {
+      /**
+       * Which section: accounts | labels | filters | addressFlags | settings
+       */
+      section: string;
+      /**
+       * Human key of the item - an email, a label name, a filter name
+       */
+      key: string;
+      /**
+       * created | updated | unchanged | skipped | rejected
+       */
+      verdict: string;
+      /**
+       * Why, when the verdict is skipped or rejected
+       */
+      reason?: string;
+    }
+    /**
+     * The import was refused because this configuration is not empty. The body is
+flat: `code`, `message` and `details` sit at the top level.
+
+`code: "config_not_empty"` — the configuration already holds an account, a
+label, a filter or an address flag. `details` names how many of each. Re-send
+with `onExisting: merge` to upsert instead.
+     */
+    export interface ConfigImportConflict {
+      statusCode: 409;
+      /**
+       * Error code
+       */
+      code: string;
+      /**
+       * Human-readable error message
+       */
+      message: string;
+      /**
+       * Additional error details
+       */
+      details?: Record;
+    }
     /**
      * The self-update resource: the running version, the outcome of the most recent manifest check, and the state of the current or last run. One read serves every interface state. The check block and the run block are independent by construction (RFC 037 D7).
      */
@@ -4208,6 +4367,78 @@ either way and cannot tell which it received.
       createdAt: number;
       updatedAt: number;
     }
+    /**
+     * A folder reference an import could not bind yet. Every folder in a
+configuration file is named by IMAP path, because mailbox ids are regenerated
+by each discovery, and a fresh database holds no mailboxes at all until IMAP
+has been read. The reference is recorded rather than dropped or guessed, and
+the binder writes the row it belongs to once the path resolves.
+     */
+    export interface ConfigImportUnresolvedRef {
+      /**
+       * Which piece of configuration this reference belongs to
+       */
+      kind: ConfigImportRefKind;
+      /**
+       * The account whose folders this path resolves against
+       */
+      accountId: UUID;
+      /**
+       * The IMAP path, as the exporting instance spelled it
+       */
+      folderPath: String512;
+      /**
+       * The role for a folder role, the folder path for a mailbox override, the filter id for a filter's move action
+       */
+      target: String256;
+    }
+    /**
+     * One applied configuration import (#1021). It exists because a file's folder
+references cannot bind at apply time: IMAP discovery produces the mailboxes,
+minutes to hours later, and the ids it assigns are new every run.
+
+The row keeps the document as applied — credential-stripped, like the file
+itself — so the binder can re-read the payload behind each reference instead
+of copying it, and so a person can see what was imported after the fact.
+     */
+    export interface ConfigImport {
+      /**
+       * Primary identifier
+       */
+      importId: UUID;
+      /**
+       * The configuration this file was imported into — the caller's own, never the one the file records as its provenance
+       */
+      accountConfigId: UUID;
+      /**
+       * Schema version of the document as applied, after migration
+       */
+      schemaVersion: number;
+      /**
+       * Whether every folder reference has been bound
+       */
+      state: ConfigImportState;
+      /**
+       * The document as applied. Carries no credential, for the same reason the file does not.
+       */
+      document: Record;
+      /**
+       * Folder references still waiting for a mailbox. Emptied by the binder as discovery resolves each path; an empty list is what makes the import Complete.
+       */
+      unresolvedRefs: ConfigImportUnresolvedRef[];
+      /**
+       * Epoch millis when the import was applied
+       */
+      createdAt: number;
+      /**
+       * Epoch millis when the last folder reference was bound; `0` while the import is still Pending
+       */
+      completedAt: number;
+      /**
+       * Epoch millis when the row was last written
+       */
+      updatedAt: number;
+    }
     /**
      * Typed value for a user setting. `kind` discriminates the concrete shape; a registry binds each setting name to the kind it requires.
      */
@@ -4720,6 +4951,202 @@ domain already uses"; it does not close it.
       createdAt: number;
       updatedAt: number;
     }
+    /**
+     * A calendar collection scoped to an account config (issue #15) — the CalDAV
+collection a client mounts, and the parent of every CalendarObject.
+
+`calendarId` is derived from `(accountConfigId, urlSegment)`, so the DAV path
+a client bookmarks resolves to a row without a lookup table, and provisioning
+the same collection twice writes the same row instead of a second one.
+`displayName` is the mutable human overlay and is never the key.
+
+`syncSequence` is the collection's monotonic change counter: every write
+through the calendar service's put path bumps it and stamps the new value on
+the object it wrote, which is what a later WebDAV-Sync `sync-token` reports
+and what `CalendarObject.bySyncSequence` pages by.
+     */
+    export interface CalendarCollection {
+      /**
+       * Primary identifier, derived from accountConfigId + urlSegment
+       */
+      calendarId: UUID;
+      /**
+       * Owning account configuration
+       */
+      accountConfigId: UUID;
+      /**
+       * Path segment this collection is addressed by, unique within the account config. Stored case-folded, the same folding `calendarId` is derived from — a DAV path is matched case-insensitively, and storing the writer's casing would let a lookup by segment and a lookup by derived id disagree about one path. The default collection provisioned on first use holds "default".
+       */
+      urlSegment: String64;
+      /**
+       * Human-readable collection name (display)
+       */
+      displayName: String140;
+      /**
+       * Display color slot for this collection
+       */
+      color: CalendarColor;
+      /**
+       * Which iCalendar components this collection accepts
+       */
+      componentSet: CalendarComponentSet;
+      /**
+       * Where this collection came from
+       */
+      source: CalendarSource;
+      /**
+       * IANA time zone this collection's floating times are read in, e.g. "Europe/Amsterdam". `""` when none is set, which reads as UTC.
+       */
+      timezone: String64;
+      /**
+       * Monotonic change counter for this collection. Bumped by every write to one of its objects; the value stamped on `CalendarObject.syncSequence` is the value this counter held after that write.
+       */
+      syncSequence: number;
+      createdAt: number;
+      updatedAt: number;
+    }
+    /**
+     * One calendar resource — the bytes behind one `.ics` URL (issue #15).
+
+`icalData` is the canonical value. Every other column on this row is a
+projection of it, computed on write and never written independently: a reader
+that needs a fact the projection does not carry re-parses `icalData` rather
+than adding a column that could disagree with it.
+
+The write path parses the bytes to validate and project them and then stores
+the bytes it was handed, never a reserialization of them. That is what keeps
+`etag` honest: the tag is a digest of exactly what the writer sent, so it
+moves only when a writer sends something different. It is not a digest that
+survives a round trip through the parser — ical.js refolds long lines and
+reorders properties, so a resource stored as its own reserialization would
+change tag without anyone editing it, and every client's cache would miss.
+
+`calendarObjectId` is derived from `(calendarId, resourceName)`: the resource
+name is the last path segment of the resource's URL, so the URL a client holds
+resolves to a row directly, and a repeated PUT of the same resource rewrites
+its own row.
+     */
+    export interface CalendarObject {
+      /**
+       * Primary identifier, derived from calendarId + resourceName
+       */
+      calendarObjectId: UUID;
+      /**
+       * Collection this resource belongs to
+       */
+      calendarId: UUID;
+      /**
+       * Last path segment of the resource's URL, e.g. "a1b2c3.ics". Unique within the collection and chosen by whoever wrote the resource, never derived from its contents — a client is free to rename a resource without changing the event it holds.
+       */
+      resourceName: String256;
+      /**
+       * The VEVENT's UID property (RFC 5545 3.8.4.7). Identifies the event across collections and servers, which `resourceName` does not.
+       */
+      icalUid: String512;
+      /**
+       * The complete VCALENDAR text, byte-for-byte as stored — CANONICAL. Line endings are CRLF and are never normalized; unknown properties and components are preserved verbatim.
+       */
+      icalData: string;
+      /**
+       * Strong entity tag over the stored `icalData` bytes, used for If-Match on a conditional write and for change detection on read.
+       */
+      etag: String64;
+      /**
+       * The VEVENT's SEQUENCE property (RFC 5545 3.8.7.4) — the organizer's own revision counter, carried for scheduling comparisons. `0` when the event declares none, which is the RFC default.
+       */
+      sequence: number;
+      /**
+       * Value the owning collection's `syncSequence` held after the write that produced this row. Pages the `bySyncSequence` read.
+       */
+      syncSequence: number;
+      /**
+       * Projection of the VEVENT's SUMMARY (RFC 5545 3.8.1.12). `""` when the event carries none.
+       */
+      summary: String512;
+      /**
+       * Projection of the master VEVENT's DTSTART as an ISO 8601 date-time with zone offset — a business date, not an epoch instant. An all-day event carries midnight in the event's own zone.
+       */
+      dtStart: String64;
+      /**
+       * Projection of the master VEVENT's effective end as an ISO 8601 date-time with zone offset, resolved from DTEND or from DTSTART + DURATION. An event with neither ends when it starts (RFC 5545 3.6.1).
+       */
+      dtEnd: String64;
+      /**
+       * Whether the master VEVENT's DTSTART is a DATE rather than a DATE-TIME (RFC 5545 3.3.4) — an all-day or multi-day event, whose end is exclusive.
+       */
+      allDay: boolean;
+      /**
+       * How the master VEVENT's DTSTART was placed on the clock. `Ambiguous` means the resource named a zone nothing could resolve, so `dtStart` and every occurrence expanded from it may be off by hours — a client shows the event and says so rather than presenting a guess as a fact.
+       */
+      zoneCertainty: ZoneCertainty;
+      /**
+       * Projection of the master VEVENT's STATUS
+       */
+      status: CalendarEventStatus;
+      /**
+       * Projection of the master VEVENT's TRANSP
+       */
+      transparency: CalendarTransparency;
+      /**
+       * Whether the resource expands to more than its master instance — an RRULE, an RDATE, or an override VEVENT. Overrides count on their own: a client that edits one instance and then drops the rule leaves a resource with a master and its exceptions, and each of those is still an occurrence.
+       */
+      hasRecurrence: boolean;
+      /**
+       * ISO 8601 UTC instant through which `CalendarEventIndex` rows exist for this resource, when the series runs past the expansion horizon and the index is therefore incomplete. `""` when the index is exhaustive — a single event, or a series that ends inside the horizon. A later live-expansion pass reads this to find the resources whose instances it must compute rather than query.
+       */
+      expandedThrough: String64;
+      createdAt: number;
+      updatedAt: number;
+    }
+    /**
+     * One occurrence of a CalendarObject, flattened so a date range can be queried
+instead of expanded (issue #15). Every row is derived from
+`CalendarObject.icalData` and is replaced wholesale whenever that resource is
+written — nothing here is authoritative, and nothing writes here alone.
+
+`recurrenceId` is `""` for a resource that does not recur — its one row. A
+resource that does recur has no `""` row at all: every occurrence carries its
+own RECURRENCE-ID slot, the first one included, so an occurrence is
+addressable without a caller having to know whether it happened to be the
+series' first. It is part of the sort key, so it can never be absent — an
+optional value there would make the index sparse and hide the single-event
+row from the range read that has to return it.
+
+Times here are UTC instants, unlike `CalendarObject.dtStart`, which carries
+the event's own offset. The two are different jobs: `dtStart` is the value a
+client displays, and a fixed-width UTC instant is the only form in which a
+sort key orders correctly — comparing offset-bearing strings would sort
+`09:00+02:00` after `09:00Z`, and a range read would silently drop
+occurrences from every zone but its own.
+     */
+    export interface CalendarEventIndex {
+      /**
+       * Collection this occurrence belongs to
+       */
+      calendarId: UUID;
+      /**
+       * Resource this occurrence was expanded from
+       */
+      calendarObjectId: UUID;
+      /**
+       * RECURRENCE-ID of this occurrence as an ISO 8601 UTC instant, or `""` for the one row of a resource that does not recur. Canonicalized to UTC by the same rule the expansion uses, so an override's RECURRENCE-ID and the occurrence it replaces resolve to the same value.
+       */
+      recurrenceId: String64;
+      /**
+       * When this occurrence starts, as an ISO 8601 UTC instant. An all-day occurrence starts at midnight of its civil date read in the collection's timezone.
+       */
+      startAt: String64;
+      /**
+       * When this occurrence ends, as an ISO 8601 UTC instant. Exclusive for an all-day occurrence, per RFC 5545 3.6.1.
+       */
+      endAt: String64;
+      /**
+       * Whether this occurrence is all-day, copied from the resource it came from so a range read never has to join back to it. A client renders an all-day occurrence as the civil date its start falls on in the collection's timezone, not as the instant stored here.
+       */
+      allDay: boolean;
+      createdAt: number;
+      updatedAt: number;
+    }
     /**
      * Junction whose existence *is* a label assignment (RFC 030). Holds only ids
 and is hydrated with `batchGet`. Keyed by a deterministic UUID v5 derived
@@ -4849,6 +5276,14 @@ declare namespace Paths {
       export type $200 = void;
     }
   }
+  namespace ImportConfig {
+    export type RequestBody = Components.Schemas.ImportConfigInput;
+    namespace Responses {
+      export type $200 = void;
+      export type $400 = void;
+      export type $409 = void;
+    }
+  }
   namespace GetSystemUpdate {
     export interface QueryParameters {
       refresh?: boolean;
@@ -5402,6 +5837,14 @@ export interface OperationMethods {
     data?: any,
     config?: AxiosRequestConfig
   ): OperationResponse<Paths.ExportConfig.Responses.$200>;
+  /**
+   * importConfig - Validate, or validate and apply, a config document. `mode: validate` (the default) writes nothing and returns the same report an apply would. `onExisting: abort` (the default) refuses with 409 when this configuration already holds accounts, labels, filters or address flags. Nothing is written until the whole document has validated; a write failure after that aborts the remainder and the report names exactly what landed. Imported accounts arrive inactive with `connectionState: credentials_missing` (or `reauth_required` for OAuth) - the credentials the file deliberately omits are re-entered per account afterwards.
+   */
+  'importConfig'(
+    parameters?: Parameters<UnknownParamsObject> | null,
+    data?: Paths.ImportConfig.RequestBody,
+    config?: AxiosRequestConfig
+  ): OperationResponse<Paths.ImportConfig.Responses.$200>;
   /**
    * getSystemUpdate - Read the self-update resource: the running version, the outcome of the most recent manifest check, and the state of the current or last run. With `refresh=true`, records a check request on the control volume for the updater to pick up and answers with the stored state as it stands; the caller watches `check.lastCheckedAt` for the updater's answer. Owner-only, and absent (404) unless a manifest URL is configured (RFC 037 D7, D8).
    */
@@ -5939,6 +6382,16 @@ export interface PathsDictionary {
       config?: AxiosRequestConfig
     ): OperationResponse<Paths.ExportConfig.Responses.$200>;
   };
+  ['/config/import']: {
+    /**
+     * importConfig - Validate, or validate and apply, a config document. `mode: validate` (the default) writes nothing and returns the same report an apply would. `onExisting: abort` (the default) refuses with 409 when this configuration already holds accounts, labels, filters or address flags. Nothing is written until the whole document has validated; a write failure after that aborts the remainder and the report names exactly what landed. Imported accounts arrive inactive with `connectionState: credentials_missing` (or `reauth_required` for OAuth) - the credentials the file deliberately omits are re-entered per account afterwards.
+     */
+    'post'(
+      parameters?: Parameters<UnknownParamsObject> | null,
+      data?: Paths.ImportConfig.RequestBody,
+      config?: AxiosRequestConfig
+    ): OperationResponse<Paths.ImportConfig.Responses.$200>;
+  };
   ['/system/update']: {
     /**
      * getSystemUpdate - Read the self-update resource: the running version, the outcome of the most recent manifest check, and the state of the current or last run. With `refresh=true`, records a check request on the control volume for the updater to pick up and answers with the stored state as it stands; the caller watches `check.lastCheckedAt` for the updater's answer. Owner-only, and absent (404) unless a manifest URL is configured (RFC 037 D7, D8).
@@ -6522,7 +6975,12 @@ export type AccountResponse = Components.Schemas.AccountResponse;
 export type AddressFlagBase = Components.Schemas.AddressFlagBase;
 export type MutedFlag = Components.Schemas.MutedFlag;
 export type FolderAppointment = Components.Schemas.FolderAppointment;
+export type PendingConfigImport = Components.Schemas.PendingConfigImport;
 export type ConfigExportResponse = Components.Schemas.ConfigExportResponse;
+export type ImportConfigInput = Components.Schemas.ImportConfigInput;
+export type ConfigImportReport = Components.Schemas.ConfigImportReport;
+export type ConfigImportItemReport = Components.Schemas.ConfigImportItemReport;
+export type ConfigImportConflict = Components.Schemas.ConfigImportConflict;
 export type SystemUpdateResponse = Components.Schemas.SystemUpdateResponse;
 export type SystemUpdateCheck = Components.Schemas.SystemUpdateCheck;
 export type SystemUpdateRun = Components.Schemas.SystemUpdateRun;
@@ -6611,6 +7069,8 @@ export type UpdateMessageLabelsInput = Components.Schemas.UpdateMessageLabelsInp
 export type SpamReportBulkResult = Components.Schemas.SpamReportBulkResult;
 export type SpamReportFailure = Components.Schemas.SpamReportFailure;
 export type EnvelopeAddress = Components.Schemas.EnvelopeAddress;
+export type ConfigImportUnresolvedRef = Components.Schemas.ConfigImportUnresolvedRef;
+export type ConfigImport = Components.Schemas.ConfigImport;
 export type AccountSettingValue = Components.Schemas.AccountSettingValue;
 export type BooleanSetting = Components.Schemas.BooleanSetting;
 export type StringSetting = Components.Schemas.StringSetting;
@@ -6632,6 +7092,9 @@ export type BodyPartParameter = Components.Schemas.BodyPartParameter;
 export type RawMessageStorage = Components.Schemas.RawMessageStorage;
 export type BodyPartStorage = Components.Schemas.BodyPartStorage;
 export type BodyPartContent = Components.Schemas.BodyPartContent;
+export type CalendarCollection = Components.Schemas.CalendarCollection;
+export type CalendarObject = Components.Schemas.CalendarObject;
+export type CalendarEventIndex = Components.Schemas.CalendarEventIndex;
 export type MessageLabel = Components.Schemas.MessageLabel;
 export type FilterAnchor = Components.Schemas.FilterAnchor;
 export type MicrosoftOAuthStartRequest = Components.Schemas.MicrosoftOAuthStartRequest;
@@ -6646,6 +7109,8 @@ export type AccountAuthType = Components.Schemas.AccountAuthType;
 export type ConnectionState = Components.Schemas.ConnectionState;
 export type SyncPhase = Components.Schemas.SyncPhase;
 export type FolderAppointmentSource = Components.Schemas.FolderAppointmentSource;
+export type ConfigImportMode = Components.Schemas.ConfigImportMode;
+export type ConfigImportOnExisting = Components.Schemas.ConfigImportOnExisting;
 export type SystemUpdateCheckStatus = Components.Schemas.SystemUpdateCheckStatus;
 export type SystemUpdatePhase = Components.Schemas.SystemUpdatePhase;
 export type SystemUpdateOutcome = Components.Schemas.SystemUpdateOutcome;
@@ -6687,6 +7152,14 @@ export type MailboxAttribute = Components.Schemas.MailboxAttribute;
 export type StorageType = Components.Schemas.StorageType;
 export type ContentEncoding = Components.Schemas.ContentEncoding;
 export type AccountSettingName = Components.Schemas.AccountSettingName;
+export type ConfigImportState = Components.Schemas.ConfigImportState;
+export type ConfigImportRefKind = Components.Schemas.ConfigImportRefKind;
+export type CalendarColor = Components.Schemas.CalendarColor;
+export type CalendarComponentSet = Components.Schemas.CalendarComponentSet;
+export type CalendarSource = Components.Schemas.CalendarSource;
+export type CalendarEventStatus = Components.Schemas.CalendarEventStatus;
+export type CalendarTransparency = Components.Schemas.CalendarTransparency;
+export type ZoneCertainty = Components.Schemas.ZoneCertainty;
 export type MessagePlacementMoveState = Components.Schemas.MessagePlacementMoveState;
 export type FlagPushOperation = Components.Schemas.FlagPushOperation;
 export type MessageFlagPushState = Components.Schemas.MessageFlagPushState;