@remit/api-openapi-types 0.0.73 → 0.0.75

package/package.json

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

package/types.d.ts

@@ -4189,6 +4189,14 @@ garbage, which is the only thing the sweep needs to know.
        * Whether the bytes have arrived
        */
       state: OutboxAttachmentState;
+      /**
+       * Content-ID the body refers to this file by, as `cid:<contentId>`
+       */
+      contentId: String256;
+      /**
+       * URL the composer fetches the stored bytes from, the same /content route a received part is read through
+       */
+      contentUrl: string;
     }
     /**
      * Input for updating a draft outbox message
@@ -4277,6 +4285,10 @@ either way and cannot tell which it received.
        * Reserved size. The upload must carry exactly this many bytes.
        */
       sizeBytes: number;
+      /**
+       * Content-ID the body refers to this file by, as `cid:<contentId>`. A file the HTML body refers to goes out inline.
+       */
+      contentId: String256;
       /**
        * Where to PUT the raw bytes. Single use, one attachment, expires.
        */
@@ -5570,6 +5582,10 @@ and no message may make that change without them.
        * How the user answers. `Tentative` adds the event as a maybe. Refused with 400 on a `Cancel` suggestion, which has nothing to answer tentatively.
        */
       answer?: CalendarInviteAnswer;
+      /**
+       * Corrections the reader made before adding it, applied to the invitation's master VEVENT. A field left out keeps what the invitation said; omitted, the invitation is added as it arrived. Refused with 400 on a `Cancel` suggestion, which names no event to correct.
+       */
+      event?: UpdateCalendarEventInput;
     }
     /**
      * Body of `POST /calendar-suggestions/{suggestionId}/dismiss`.